npm-audit-report 2.1.3
Given a response from the npm security api, render it into a variety of security reports
npm-audit-report@2.1.3 was published on 2020-07-17. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.
All npm-audit-report versions · Permanent reference to 2.1.3 · View npm registry JSON · Latest release
Package specifications
| Version | 2.1.3 |
|---|---|
| License declaration | ISC |
| Published | 2020-07-17T22:41:54.153Z |
| Node.js requirement | >=10 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 14.33 KiB |
| Published file count | 11 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 37 |
| Repository forks | 20 |
Install npm-audit-report 2.1.3
npm install npm-audit-report@2.1.3 pnpm add npm-audit-report@2.1.3 yarn add npm-audit-report@2.1.3
Runtime dependencies
- chalk ^4.0.0
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.
- ansi-styles@4.3.0 — indirect
- chalk@4.1.2 — direct
- color-convert@2.0.1 — indirect
- color-name@1.1.4 — indirect
- has-flag@4.0.0 — indirect
- supports-color@7.2.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.
| Code-Review | 10/10 — all changesets reviewed |
|---|---|
| Maintained | 0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
| 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 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| SAST | 8/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-06T02:28:12.489Z
- https://api.deps.dev/v3/systems/npm/packages/npm-audit-report/versions/2.1.3:dependencies — retrieved 2026-11-06T02:28:12.594Z
- https://api.deps.dev/v3/systems/npm/packages/npm-audit-report/versions/2.1.3 — retrieved 2026-11-06T02:28:12.634Z
- https://api.deps.dev/v3/projects/github.com%2Fnpm%2Fnpm-audit-report — retrieved 2026-11-05T17:59:36.744Z (stale snapshot; refresh pending)