husky 0.14.0
Prevents bad commit or push (git hooks, pre-commit/precommit, pre-push/prepush, post-merge/postmerge and all that stuff...)
husky@0.14.0 was published on 2017-06-22. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.
All husky versions · Permanent reference to 0.14.0 · Latest release
Package specifications
| Version | 0.14.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-06-22T18:14:57.000Z |
| Node.js requirement | >=4 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 35367 |
| Repository forks | 1102 |
Install husky 0.14.0
npm install husky@0.14.0 pnpm add husky@0.14.0 yarn add husky@0.14.0
Runtime dependencies
- is-ci ^1.0.10
- strip-indent ^2.0.0
- normalize-path ^1.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- ci-info@1.6.0 — indirect
- is-ci@1.2.1 — direct
- normalize-path@1.0.0 — direct
- strip-indent@2.0.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 3/10 — Found 9/30 approved changesets -- score normalized to 3 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Pinned-Dependencies | 1/10 — dependency not pinned by hash detected -- score normalized to 1 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/husky/0.14.0 — retrieved 2026-10-31T18:19:35.931Z
- https://api.deps.dev/v3/projects/github.com%2Ftypicode%2Fhusky — retrieved 2026-10-31T15:04:15.643Z
- https://api.deps.dev/v3/systems/npm/packages/husky/versions/0.14.0 — retrieved 2026-10-31T18:19:36.431Z
- https://api.deps.dev/v3/systems/npm/packages/husky/versions/0.14.0:dependencies — retrieved 2026-10-31T18:19:36.449Z