typicode/husky

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.