npm-check
Check for outdated, incorrect, and unused dependencies.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed back to dylang, the original author and repo owner. Legitimate maintainer activity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature utility with infrequent updates; 868-day gap is normal for stable CLI tools. Original author published. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; no CI/CD attestation is expected for this era of tooling. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Hardcoded literal used for ES2015 arrow-function feature detection; not dynamic code execution from user input. Stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load package.json files from user-specified paths — core functionality of a dependency-checking tool, not arbitrary module loading from untrusted input. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 27 / 6 | |
| 5.9.2 | 26 / 4 | |
| 5.9.1 | 26 / 4 | |
| 5.9.0 | 26 / 4 | |
| 5.8.0 | 26 / 4 | |
| 5.7.1 | 25 / 4 | |
| 5.7.0 | 25 / 4 | |
| 5.6.0 | 25 / 4 | |
| 5.5.2 | 25 / 4 | |
| 5.5.1 | 25 / 4 | |
| 5.5.0 | 25 / 4 | |
| 5.4.5 | 25 / 4 | |
| 5.4.4 | 25 / 4 | |
| 5.4.3 | 26 / 4 | |
| 5.4.2 | 25 / 4 | |
| 5.4.0 | 25 / 9 | |
| 5.3.0 | 24 / 9 | |
| 5.2.3 | 23 / 9 | |
| 5.2.2 | 23 / 9 | |
| 5.2.1 | 23 / 9 | |
| 5.2.0 | 23 / 9 | |
| 5.1.3 | 22 / 6 | |
| 5.1.2 | 22 / 6 | |
| 5.1.1 | 22 / 6 | |
| 5.1.0 | 22 / 6 | |
| 5.0.3 | 20 / 6 | |
| 5.0.2 | 19 / 6 | |
| 5.0.1 | 19 / 6 | |
| 4.1.4 | 18 / 9 | |
| 4.1.3 | 18 / 9 | |
| 4.1.2 | 18 / 9 | |
| 4.1.1 | 18 / 9 | |
| 4.1.0 | 18 / 9 | |
| 4.0.4 | 18 / 9 | |
| 4.0.3 | 18 / 9 | |
| 4.0.2 | 17 / 9 | |
| 4.0.1 | 18 / 8 | |
| 4.0.0 | 18 / 8 | |
| 3.2.10 | 16 / 6 | |
| 3.2.9 | 16 / 6 | |
| 3.2.7 | 16 / 6 | |
| 3.2.6 | 15 / 6 | |
| 3.2.5 | 15 / 6 | |
| 3.2.4 | 15 / 6 | |
| 3.2.3 | 15 / 6 | |
| 3.2.2 | 15 / 6 | |
| 3.2.1 | 15 / 6 | |
| 3.0.0 | 15 / 6 | |
| 2.0.0 | 10 / 6 | |
| 1.0.2 | 10 / 5 | |
| 1.0.0 | 10 / 5 | |
| 0.0.4 | 10 / 5 | |
| 0.0.3 | 12 / 5 | |
| 0.0.2 | 12 / 5 | |
| 0.0.1 | 12 / 5 |
v6.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-07-15. This could indicate a legitimate maintainer transition or an account compromise.
v5.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-11. This could indicate a legitimate maintainer transition or an account compromise.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-06-20. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.