husky 1.1.2
Prevents bad commit or push (git hooks, pre-commit/precommit, pre-push/prepush, post-merge/postmerge and all that stuff...)
husky@1.1.2 was published on 2018-10-11. Its manifest declares 10 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All husky versions · Permanent reference to 1.1.2 · Latest release
Package specifications
| Version | 1.1.2 |
|---|---|
| License declaration | MIT |
| Published | 2018-10-11T02:01:37.310Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 10 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 33.22 KiB |
| Published file count | 18 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 62 |
| Repository stars | 35367 |
| Repository forks | 1102 |
Install husky 1.1.2
npm install husky@1.1.2 pnpm add husky@1.1.2 yarn add husky@1.1.2
Runtime dependencies
- execa ^0.9.0
- is-ci ^1.2.1
- slash ^2.0.0
- find-up ^3.0.0
- pkg-dir ^3.0.0
- read-pkg ^4.0.1
- run-node ^1.0.0
- get-stdin ^6.0.0
- cosmiconfig ^5.0.6
- please-upgrade-node ^3.1.1
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.
- argparse@1.0.10 — indirect
- caller-callsite@2.0.0 — indirect
- caller-path@2.0.0 — indirect
- callsites@2.0.0 — indirect
- ci-info@1.6.0 — indirect
- cosmiconfig@5.2.1 — direct
- cross-spawn@5.1.0 — indirect
- error-ex@1.3.4 — indirect
- es-errors@1.3.0 — indirect
- esprima@4.0.1 — indirect
- execa@0.9.0 — direct
- find-up@3.0.0 — direct
- function-bind@1.1.2 — indirect
- get-stdin@6.0.0 — direct
- get-stream@3.0.0 — indirect
- hasown@2.0.4 — indirect
- hosted-git-info@2.8.9 — indirect
- import-fresh@2.0.0 — indirect
- is-arrayish@0.2.1 — indirect
- is-ci@1.2.1 — direct
- is-core-module@2.17.0 — indirect
- is-directory@0.3.1 — indirect
- is-stream@1.1.0 — indirect
- isexe@2.0.0 — indirect
- js-yaml@3.15.2 — indirect
- json-parse-better-errors@1.0.2 — indirect
- locate-path@3.0.0 — indirect
- lru-cache@4.1.5 — indirect
- normalize-package-data@2.5.0 — indirect
- npm-run-path@2.0.2 — indirect
- p-finally@1.0.0 — indirect
- p-limit@2.3.0 — indirect
- p-locate@3.0.0 — indirect
- p-try@2.2.0 — indirect
- parse-json@4.0.0 — indirect
- path-exists@3.0.0 — indirect
- path-key@2.0.1 — indirect
- path-parse@1.0.7 — indirect
- pify@3.0.0 — indirect
- pkg-dir@3.0.0 — direct
- please-upgrade-node@3.2.0 — direct
- pseudomap@1.0.2 — indirect
- read-pkg@4.0.1 — direct
- resolve@1.22.13 — indirect
- resolve-from@3.0.0 — indirect
- run-node@1.0.0 — direct
- semver@5.7.2 — indirect
- semver-compare@1.0.0 — indirect
- shebang-command@1.2.0 — indirect
- shebang-regex@1.0.0 — indirect
- signal-exit@3.0.7 — indirect
- slash@2.0.0 — direct
- spdx-correct@3.2.0 — indirect
- spdx-exceptions@2.5.0 — indirect
- spdx-expression-parse@3.0.1 — indirect
- spdx-license-ids@3.0.24 — indirect
- sprintf-js@1.0.3 — indirect
- strip-eof@1.0.0 — indirect
- supports-preserve-symlinks-flag@1.0.0 — indirect
- validate-npm-package-license@3.0.4 — indirect
- which@1.3.1 — indirect
- yallist@2.1.2 — indirect
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/1.1.2 — retrieved 2026-10-31T14:49:21.197Z
- https://api.deps.dev/v3/projects/github.com%2Ftypicode%2Fhusky — retrieved 2026-10-31T08:56:38.738Z
- https://api.deps.dev/v3/systems/npm/packages/husky/versions/1.1.2 — retrieved 2026-10-31T14:49:21.633Z
- https://api.deps.dev/v3/systems/npm/packages/husky/versions/1.1.2:dependencies — retrieved 2026-10-31T14:49:21.660Z