dotnet-deps-parser 4.9.1

Generate a dep tree given a collection of manifests

dotnet-deps-parser@4.9.1 was published on 2019-12-19. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=4.

All dotnet-deps-parser versions · Permanent reference to 4.9.1 · Latest release

Package specifications

Version4.9.1
License declarationApache-2.0
Published2019-12-19T09:53:36.065Z
Node.js requirement>=4
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size50.77 KiB
Published file count18
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies108
Repository stars12
Repository forks8

Install dotnet-deps-parser 4.9.1

npm install dotnet-deps-parser@4.9.1
pnpm add dotnet-deps-parser@4.9.1
yarn add dotnet-deps-parser@4.9.1

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-Review8/10 — Found 24/29 approved changesets -- score normalized to 8
Security-Policy9/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained4/10 — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge 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