cover
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:contrib/esprima.js | AI (source-diff): contrib/esprima.js is the well-known esprima JS parser bundled as a single minified file — a legitimate and expected distribution pattern for this code coverage tool. | ai | |
| phantom-deps | phantom-dep:compress-buffer | AI (phantom-deps): compress-buffer is a declared optional/config-referenced dep in this legacy package; not a malicious phantom dependency. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in contrib/colors.js is a theme-loading mechanism, not arbitrary code execution. Stable benign pattern for this package. | ai | |
| phantom-deps | phantom-dep:which | AI (phantom-deps): Declared dependency referenced in config/tooling context only; not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:cli-table | AI (phantom-deps): Declared dependency referenced in config/tooling context only; not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:underscore.string | AI (phantom-deps): Declared dependency referenced in config/tooling context only; not a security concern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.9 | 4 / 0 | |
| 0.2.8 | 4 / 0 | |
| 0.2.7 | 4 / 0 | |
| 0.2.6 | 4 / 0 | |
| 0.2.5 | 5 / 0 | |
| 0.2.4 | 4 / 0 | |
| 0.2.3 | 4 / 0 | |
| 0.2.2 | 4 / 0 | |
| 0.2.1 | 4 / 0 | |
| 0.2.0 | 4 / 0 | |
| 0.1.0 | 4 / 0 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 6 / 0 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.