resolve-package-path 2.0.0
a special purpose fast memoizing way to resolve a node modules package.json
resolve-package-path@2.0.0 was published on 2019-12-09. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is 8.* || 10.* || >= 12.
All resolve-package-path versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-12-09T18:35:12.427Z |
| Node.js requirement | 8.* || 10.* || >= 12 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 106.02 KiB |
| Published file count | 31 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 9 |
| Repository stars | 32 |
| Repository forks | 10 |
Install resolve-package-path 2.0.0
npm install resolve-package-path@2.0.0 pnpm add resolve-package-path@2.0.0 yarn add resolve-package-path@2.0.0
Runtime dependencies
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.
- es-errors@1.3.0 — indirect
- function-bind@1.1.2 — indirect
- hasown@2.0.4 — indirect
- is-core-module@2.17.0 — indirect
- path-parse@1.0.7 — indirect
- path-root@0.1.1 — direct
- path-root-regex@0.1.2 — indirect
- resolve@1.22.13 — direct
- supports-preserve-symlinks-flag@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.
| 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 |
| Code-Review | 1/10 — Found 2/15 approved changesets -- score normalized to 1 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- 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 |
| Security-Policy | 0/10 — security policy file not detected |
| 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/resolve-package-path/2.0.0 — retrieved 2026-10-29T08:43:38.160Z
- https://api.deps.dev/v3/systems/npm/packages/resolve-package-path/versions/2.0.0 — retrieved 2026-10-29T08:43:38.651Z
- https://api.deps.dev/v3/systems/npm/packages/resolve-package-path/versions/2.0.0:dependencies — retrieved 2026-10-29T08:43:38.669Z
- https://api.deps.dev/v3/projects/github.com%2Fstefanpenner%2Fresolve-package-path — retrieved 2026-10-29T08:43:39.241Z