pinst 1.1.0
Enable or disable npm postinstall hook
pinst@1.1.0 was published on 2018-06-11. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All pinst versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-06-11T18:59:26.254Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 7.36 KiB |
| Published file count | 8 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 65 |
| Repository stars | 263 |
| Repository forks | 8 |
Install pinst 1.1.0
npm install pinst@1.1.0 pnpm add pinst@1.1.0 yarn add pinst@1.1.0
Runtime dependencies
- load-json-file ^5.0.0
- lodash.mapkeys ^4.6.0
- meow ^5.0.0
- write-json-file ^2.3.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.
- load-json-file@5.3.0 — direct
- lodash.mapkeys@4.6.0 — direct
- meow@5.0.0 — direct
- write-json-file@2.3.0 — direct
- graceful-fs@4.2.11 — indirect
- parse-json@4.0.0 — indirect
- pify@4.0.1 — indirect
- strip-bom@3.0.0 — indirect
- type-fest@0.3.1 — indirect
- camelcase-keys@4.2.0 — indirect
- decamelize-keys@1.1.1 — indirect
- loud-rejection@1.6.0 — indirect
- minimist-options@3.0.2 — indirect
- normalize-package-data@2.5.0 — indirect
- read-pkg-up@3.0.0 — indirect
- redent@2.0.0 — indirect
- trim-newlines@2.0.0 — indirect
- yargs-parser@10.1.0 — indirect
- detect-indent@5.0.0 — indirect
- make-dir@1.3.0 — indirect
- pify@3.0.0 — indirect
- sort-keys@2.0.0 — indirect
- write-file-atomic@2.4.3 — indirect
- error-ex@1.3.4 — indirect
- json-parse-better-errors@1.0.2 — indirect
- camelcase@4.1.0 — indirect
- map-obj@2.0.0 — indirect
- quick-lru@1.1.0 — indirect
- decamelize@1.2.0 — indirect
- map-obj@1.0.1 — indirect
- currently-unhandled@0.4.1 — indirect
- signal-exit@3.0.7 — indirect
- arrify@1.0.1 — indirect
- is-plain-obj@1.1.0 — indirect
- hosted-git-info@2.8.9 — indirect
- resolve@1.22.13 — indirect
- semver@5.7.2 — indirect
- validate-npm-package-license@3.0.4 — indirect
- find-up@2.1.0 — indirect
- read-pkg@3.0.0 — indirect
- indent-string@3.2.0 — indirect
- strip-indent@2.0.0 — indirect
- pify@3.0.0 — indirect
- imurmurhash@0.1.4 — indirect
- is-arrayish@0.2.1 — indirect
- array-find-index@1.0.2 — indirect
- es-errors@1.3.0 — indirect
- is-core-module@2.17.0 — indirect
- path-parse@1.0.7 — indirect
- supports-preserve-symlinks-flag@1.0.0 — indirect
- spdx-correct@3.2.0 — indirect
- spdx-expression-parse@3.0.1 — indirect
- locate-path@2.0.0 — indirect
- load-json-file@4.0.0 — indirect
- path-type@3.0.0 — indirect
- hasown@2.0.4 — indirect
- spdx-license-ids@3.0.24 — indirect
- spdx-exceptions@2.5.0 — indirect
- p-locate@2.0.0 — indirect
- path-exists@3.0.0 — indirect
- pify@3.0.0 — indirect
- pify@3.0.0 — indirect
- function-bind@1.1.2 — indirect
- p-limit@1.3.0 — indirect
- p-try@1.0.0 — 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 | 0/10 — Found 0/28 approved changesets -- score normalized to 0 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/pinst/1.1.0 — retrieved 2026-10-29T23:31:09.174Z
- https://api.deps.dev/v3/projects/github.com%2Ftypicode%2Fpinst — retrieved 2026-10-29T22:28:34.924Z
- https://api.deps.dev/v3/systems/npm/packages/pinst/versions/1.1.0 — retrieved 2026-10-29T23:31:09.685Z
- https://api.deps.dev/v3/systems/npm/packages/pinst/versions/1.1.0:dependencies — retrieved 2026-10-29T23:31:09.722Z