resolve-path
Resolve a relative path against a root path with validation
resolve-path@1.4.0 was published on 2018-02-13. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.
All resolve-path versions · Permanent reference to 1.4.0
Package specifications
| Version | 1.4.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-02-13T19:31:55.011Z |
| Node.js requirement | >= 0.8 |
| Type declarations | Not declared |
| 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 | 9.02 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 34 |
| Repository forks | 14 |
Install resolve-path 1.4.0
npm install resolve-path@1.4.0 pnpm add resolve-path@1.4.0 yarn add resolve-path@1.4.0
Runtime dependencies
- http-errors ~1.6.2
- path-is-absolute 1.0.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.
- depd@1.1.2 — indirect
- http-errors@1.6.3 — direct
- inherits@2.0.3 — indirect
- path-is-absolute@1.0.1 — direct
- setprototypeof@1.1.0 — indirect
- statuses@1.5.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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 0/10 — Found 1/24 approved changesets -- score normalized to 0 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| 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 | 9/10 — security policy file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 9/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/resolve-path/1.4.0 — retrieved 2026-10-29T09:56:58.369Z
- https://api.deps.dev/v3/systems/npm/packages/resolve-path/versions/1.4.0:dependencies — retrieved 2026-10-29T09:56:58.340Z
- https://api.deps.dev/v3/systems/npm/packages/resolve-path/versions/1.4.0 — retrieved 2026-10-29T09:56:58.316Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fpillarjs%2Fresolve-path — retrieved 2026-10-29T09:56:58.961Z