snyk-nodejs-lockfile-parser 2.10.5

Generate a dep tree given a lockfile

snyk-nodejs-lockfile-parser@2.10.5 was published on 2026-10-19. Its manifest declares 18 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^20.19.0 || ^22.13.0 || >=24.0.0.

All snyk-nodejs-lockfile-parser versions · Permanent reference to 2.10.5 · Latest release

Package specifications

Version2.10.5
License declarationApache-2.0
Published2026-10-19T12:54:04.323Z
Node.js requirement^20.19.0 || ^22.13.0 || >=24.0.0
Type declarationsBundled declarations
Runtime dependency count18
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size377.73 KiB
Published file count175
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies59
Repository stars79
Repository forks30

Install snyk-nodejs-lockfile-parser 2.10.5

npm install snyk-nodejs-lockfile-parser@2.10.5
pnpm add snyk-nodejs-lockfile-parser@2.10.5
yarn add snyk-nodejs-lockfile-parser@2.10.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.

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-Review9/10 — Found 11/12 approved changesets -- score normalized to 9
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness