Discofork
Repository brief

typicode/husky

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:52:20.134Z
1mo ago

typicode/husky

typicode/husky is a popular Node.js package for making Git hooks easy. It is actively maintained, not archived, and currently at version 9.1.7 with a large user base (34,910 stars, 1,081 forks).

GitHub
Loading tags...
Stars34,910
Forks1,081
Default branchmain
Last pushed2026-03-19T23:03:16Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

9 of 9 fork briefs
Selected

Choose this fork only if you specifically need its legacy Yorkie behavior; otherwise upstream Husky is the better default because it is actively maintained and much more current.

Choose this fork only if Mercurial support is the requirement. If you just need modern Git hooks, upstream Husky is the safer choice because it is active and current; this fork is mainly for legacy mixed-VCS environments.

Choose the upstream project unless you specifically need this fork's older initialization and shell-loading behavior. This fork looks best for legacy compatibility or pinning a known workflow, not for users who want current Husky maintenance.

Prefer upstream unless you specifically need a frozen historical copy; this fork adds no visible capability and is far behind current Husky maintenance.

Choose this fork only if you need an older, customized Husky for legacy projects. If you want the current supported product, upstream is the better choice.

Choose upstream unless you specifically want a personal fork to modify. This fork does not appear to add capabilities, and it is slightly behind current upstream maintenance.

Prefer upstream unless you specifically want the docs dependency updates in this fork. This fork does not appear to improve the core Husky experience, and it is behind upstream enough that it is better suited as a maintenance branch than as a general replacement.

Prefer upstream unless you specifically need this exact historical snapshot; this fork adds no visible capabilities and is materially stale.

Prefer upstream for active maintenance and lower risk. Choose this fork only if you specifically need its repo-level doc tweak and are willing to maintain the gap yourself.

typicode/husky · Discofork