Shuck
a fast shell linter written in Rust
Details
- External ID
- 47963760
- Source
- HN
- Company
- —
- Product
- Shuck
- Website domain
- github.com
- Launched
- April 30, 2026
- Cohort
- —
- Upvotes
- 8
- Upvotes percentile
- 0.4813624678663239
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
I’ve been working on shuck, a shell script linter written in Rust.ShellCheck is excellent project and set the bar for this space. However, it's very slow and take up a far amount of resources. shuck is conservatively 20x faster than shellcheck and uses a fraction of the resources. shuck currently supports sh, bash, dash, ksh, mksh, and zsh.shuck should mostly be a drop in replacement for shellcheck but it is not a port since shellcheck is GPL. It is s clean-room implementation with its own parser and analysis engine, so behavior may differ in some cases. shuck is tested against shellcheck on a large number of open source projects with a lot of shell scripts and has very few variations.That said, I’ve tried to make migration easy: 1) shuck supports ShellCheck-style suppression 2) you can run shuck in shellcheck compatibility mode where it has all the same CLI args and output.This is still early, and I’d especially love feedback from people who maintain large monorepos, CI-heavy projects, or lots of shell scripts. I’m interested in places where ShellCheck compatibility matters, places where it does not, and which classes of shell bugs people most want lint/fix support for next.
Enrichment
- Theme
- self-hosted infrastructure and security tools
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- shell linter for rust developers
- Manually corrected
- False
Could you build this?
No Building a high-performance shell script linter in Rust that outperforms ShellCheck requires deep expertise in formal grammars, POSIX shell semantics, AST construction, and systems-level optimization.
What it would actually take: The project requires writing an incremental, resilient parser for POSIX/Bash syntax in Rust, paired with a semantic analysis engine that executes hundreds of specialized lint rules against AST and control-flow graphs. The primary difficulty lies in the notoriously complex, context-dependent syntax of shell scripts and edge-case handling across different shell dialects. It demands specialized compiler engineering and systems programming expertise.
Discussion
1 comment analyzed.
Competitors mentioned: Sublime
Concerns raised: Unusual commit velocity (1,163 commits in 3 weeks by one person)
Competitors
Other products that read as similar to this one — 186 launches clear the similarity bar, closest 8 shown.
Attention rank: #99 of 187 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 182 days after the earliest competitor.
- Grsh · hn · 2026-01-14 · 50 upvotes · similarity 0.59
- shellstrict · github · 2026-09-28 · 30 upvotes · similarity 0.55
- Kosh · hn · 2026-08-28 · 7 upvotes · similarity 0.55
- Hurry · hn · 2025-12-22 · 11 upvotes · similarity 0.49
- Afterburner · hn · 2026-06-14 · 6 upvotes · similarity 0.46
- CodeDiff · hn · 2026-09-29 · 6 upvotes · similarity 0.45
- Jitzu · hn · 2026-02-17 · 6 upvotes · similarity 0.45
- Shifu · hn · 2026-03-30 · 7 upvotes · similarity 0.45
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.