npm-paths
Returns an array of NPM directory paths based on the user's platform and environment.
npm-paths@2.0.0 was published on 2018-12-15. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All npm-paths versions · Permanent reference to 2.0.0
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-12-15T06:43:28.213Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 7.53 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 14 |
| Repository forks | 1 |
Install npm-paths 2.0.0
npm install npm-paths@2.0.0 pnpm add npm-paths@2.0.0 yarn add npm-paths@2.0.0
Runtime dependencies
- global-modules ^2.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.
- global-modules@2.0.0 — direct
- global-prefix@3.0.0 — indirect
- ini@1.3.8 — indirect
- isexe@2.0.0 — indirect
- kind-of@6.0.3 — indirect
- which@1.3.1 — 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 | 1/10 — Found 2/16 approved changesets -- score normalized to 1 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/npm-paths/2.0.0 — retrieved 2026-10-30T08:30:54.460Z
- https://api.deps.dev/v3/systems/npm/packages/npm-paths/versions/2.0.0 — retrieved 2026-10-30T08:30:55.133Z
- https://api.deps.dev/v3/systems/npm/packages/npm-paths/versions/2.0.0:dependencies — retrieved 2026-10-30T08:30:55.155Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fnpm-paths — retrieved 2026-10-30T08:30:55.361Z