resolve-dep 0.3.5
Return an array of resolved filepaths for require-able local or named npm modules. Wildcard (glob) patterns may be used.
resolve-dep@0.3.5 was published on 2014-06-23. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.10.16.
All resolve-dep versions · Permanent reference to 0.3.5 · Latest release
Package specifications
| Version | 0.3.5 |
|---|---|
| License declaration | Not declared |
| Published | 2014-06-23T22:42:32.258Z |
| Node.js requirement | >= 0.10.16 |
| Type declarations | Not declared |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 13 |
| Repository stars | 12 |
| Repository forks | 5 |
Install resolve-dep 0.3.5
npm install resolve-dep@0.3.5 pnpm add resolve-dep@0.3.5 yarn add resolve-dep@0.3.5
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.
- cwd@0.3.7 — direct
- findup-sync@0.1.3 — indirect
- glob@3.2.11 — indirect
- globule@0.2.0 — direct
- inherits@2.0.4 — indirect
- load-pkg@0.1.0 — direct
- lodash@2.4.2 — direct
- lru-cache@2.7.3 — indirect
- minimatch@0.2.14 — indirect
- minimatch@0.3.0 — indirect
- normalize-path@0.1.1 — indirect
- resolve@0.6.3 — direct
- sigmund@1.0.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.
| 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 |
| Code-Review | 0/10 — Found 2/26 approved changesets -- 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/resolve-dep/0.3.5 — retrieved 2026-10-29T23:47:13.067Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fresolve-dep — retrieved 2026-10-29T22:28:47.565Z
- https://api.deps.dev/v3/systems/npm/packages/resolve-dep/versions/0.3.5 — retrieved 2026-10-29T23:47:13.585Z
- https://api.deps.dev/v3/systems/npm/packages/resolve-dep/versions/0.3.5:dependencies — retrieved 2026-10-29T23:47:13.612Z