@npmcli/metavuln-calculator

Calculate meta-vulnerabilities from package security advisories

@npmcli/metavuln-calculator@10.0.0 was published on 2026-06-15. 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 ^22.22.2 || ^24.15.0 || >=26.0.0.

All @npmcli/metavuln-calculator versions · Permanent reference to 10.0.0

Package specifications

Version10.0.0
License declarationISC
Published2026-06-15T20:44:52.038Z
Node.js requirement^22.22.2 || ^24.15.0 || >=26.0.0
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size29.61 KiB
Published file count7
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies91
Repository stars15
Repository forks15

Install @npmcli/metavuln-calculator 10.0.0

npm install @npmcli/metavuln-calculator@10.0.0
pnpm add @npmcli/metavuln-calculator@10.0.0
yarn add @npmcli/metavuln-calculator@10.0.0

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-Review10/10 — all changesets reviewed
Security-Policy10/10 — security policy file detected
Maintained10/10 — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
SAST9/10 — SAST tool detected but not run on all commits

Evidence and freshness