lookup-deps 0.2.2
Simple API for getting metadata from locally installed npm packages (in `node_modules`).
lookup-deps@0.2.2 was published on 2014-10-24. Its manifest declares 8 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All lookup-deps versions · Permanent reference to 0.2.2 · Latest release
Package specifications
| Version | 0.2.2 |
|---|---|
| License declaration | Not declared |
| Published | 2014-10-24T17:13:05.934Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 8 |
| 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 | 69 |
| Repository stars | 11 |
| Repository forks | 1 |
Install lookup-deps 0.2.2
npm install lookup-deps@0.2.2 pnpm add lookup-deps@0.2.2 yarn add lookup-deps@0.2.2
Runtime dependencies
- deep-filter-object ^0.1.0
- filter-keys ^0.1.2
- filter-object ^0.1.1
- fs-utils ^0.6.0
- get-value ^0.3.0
- lodash ^2.4.1
- look-up ^0.1.0
- sort-object ^0.3.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.
- deep-filter-object@0.1.0 — direct
- filter-keys@0.1.2 — direct
- filter-object@0.1.3 — direct
- fs-utils@0.6.5 — direct
- get-value@0.3.2 — direct
- lodash@2.4.2 — direct
- look-up@0.1.1 — direct
- sort-object@0.3.2 — direct
- isobject@0.2.0 — indirect
- multimatch@1.0.1 — indirect
- async@1.5.2 — indirect
- delete@0.2.1 — indirect
- extend-shallow@2.0.1 — indirect
- graceful-fs@4.2.11 — indirect
- is-absolute@0.2.6 — indirect
- js-yaml@3.15.2 — indirect
- kind-of@2.0.1 — indirect
- lazy-cache@0.2.7 — indirect
- matched@0.3.2 — indirect
- normalize-path@0.3.0 — indirect
- relative@0.1.6 — indirect
- minimatch@1.0.0 — indirect
- sort-asc@0.1.0 — indirect
- sort-desc@0.1.1 — indirect
- array-differ@1.0.0 — indirect
- array-union@1.0.2 — indirect
- bluebird@2.11.0 — indirect
- lazy-cache@0.1.0 — indirect
- rimraf@2.7.1 — indirect
- is-extendable@0.1.1 — indirect
- is-relative@0.2.1 — indirect
- is-windows@0.2.0 — indirect
- argparse@1.0.10 — indirect
- esprima@4.0.1 — indirect
- is-buffer@1.1.6 — indirect
- async-array-reduce@0.1.0 — indirect
- glob@5.0.15 — indirect
- is-valid-glob@0.3.0 — indirect
- resolve-dir@0.1.1 — indirect
- normalize-path@0.1.1 — indirect
- lru-cache@2.7.3 — indirect
- sigmund@1.0.1 — indirect
- array-uniq@1.0.3 — indirect
- ansi-yellow@0.1.1 — indirect
- glob@7.2.3 — indirect
- is-unc-path@0.1.2 — indirect
- sprintf-js@1.0.3 — indirect
- inflight@1.0.6 — indirect
- inherits@2.0.4 — indirect
- minimatch@3.1.5 — indirect
- once@1.4.0 — indirect
- path-is-absolute@1.0.1 — indirect
- expand-tilde@1.2.2 — indirect
- global-modules@0.2.3 — indirect
- ansi-wrap@0.1.0 — indirect
- fs.realpath@1.0.0 — indirect
- minimatch@3.1.5 — indirect
- unc-path-regex@0.1.2 — indirect
- wrappy@1.0.2 — indirect
- brace-expansion@1.1.21 — indirect
- os-homedir@1.0.2 — indirect
- global-prefix@0.1.5 — indirect
- balanced-match@1.0.2 — indirect
- concat-map@0.0.1 — indirect
- homedir-polyfill@1.0.3 — indirect
- ini@1.3.8 — indirect
- which@1.3.1 — indirect
- parse-passwd@1.0.0 — indirect
- isexe@2.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 |
|---|---|
| Code-Review | 0/10 — Found 1/30 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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 |
| 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/lookup-deps/0.2.2 — retrieved 2026-10-30T05:05:15.575Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Flookup-deps — retrieved 2026-10-29T22:05:02.482Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/lookup-deps/versions/0.2.2 — retrieved 2026-10-30T05:05:16.090Z
- https://api.deps.dev/v3/systems/npm/packages/lookup-deps/versions/0.2.2:dependencies — retrieved 2026-10-30T05:05:16.132Z