compare
lefthook vs pre-commit
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | lefthook | pre-commit |
|---|---|---|
| Language | Go | Python |
| Licence | MIT | MIT |
| Stars | 8.9k | 16k |
| Latest | v2.1.17 | v4.6.2 |
| Last push | 2026-10-05 | 2026-10-06 |
| Release cadence | about 9 days between releases | about 58 days between releases |
| Active contributors | 22 commit authors on the default branch in the last 90 days | 3 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
lefthook replaces pre-commit. Alternatives to pre-commit →
Full replacementRuns hook commands in parallel, but uses tools you install instead of building an environment per hook.
lefthook
- v2.1.172026-10-058d8073d427fac49cc982919f5280b295645d196d fix: diff push files against the merge base with the default branch (#1565)
- v2.1.162026-10-013ee04318fd06d56a70cc9c90dc8385b19918f520 ci: refactor publishing scripts (#1559)
- v2.1.152026-09-292388dde2b31dc9a782e967764046b41b404cece9 feat: propagate forced colors to hook commands via CLICOLOR_FORCE (#1547)
- v2.1.142026-09-14
- v2.1.122026-08-28b8350fde604197b2422adfc4ae0af080725822b9 ci: fix npm publishing by bumping Node to 24 (#1508)
lefthook
✓ signed The latest release, v2.1.17, carries a signature GitHub verified.
Loading the security report
pre-commit
unsigned The latest release, v4.6.2, carries no signature GitHub could verify.
Loading the security report