c8
output coverage reports using Node.js' built in coverage
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): bcoe → oss-bot is a documented, legitimate transition for Ben Coe's packages to automated CI publishing. oss-bot has strong track record (368 approved). Stable for this package. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with the switch to automated oss-bot publishing environment. Not indicative of tampering for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): oss-bot added as maintainer is part of the legitimate bcoe → oss-bot automation transition. No compromise indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @istanbuljs/schema is a legitimate Istanbul ecosystem package; adding it to a coverage tool is expected and benign. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is properly declared in dependencies and used by c8; false positive for this package. | ai | |
| dependencies | unvetted-dep:@c88/v8-coverage | AI (dependencies): @c88 is Ben Coe's own npm scope (same author as c8); this is a first-party dependency, not a suspicious third-party package. | ai | |
| dependencies | unvetted-dep:chrome-remote-interface | AI (dependencies): chrome-remote-interface is the standard DevTools Protocol client; its use is expected and appropriate for a V8 coverage tool like c8. | ai | |
| dependencies | unvetted-dep:spawn-wrap | AI (dependencies): spawn-wrap is a well-known child process instrumentation utility; its use is expected for a coverage tool that wraps test runners. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): c8 is a well-known Node.js coverage tool, not a typosquat of qs. The name is intentional (C8/V8 coverage). | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): c8 is a well-known Node.js coverage tool, not a typosquat of pg. The name is intentional (C8/V8 coverage). | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to parse base64-encoded source map data URIs, a standard and expected operation for a coverage/source-map tool. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 11 / 8 | |
| 10.1.3 | 11 / 8 | |
| 10.1.2 | 11 / 8 | |
| 10.1.1 | 11 / 9 | |
| 10.1.0 | 11 / 8 | |
| 10.0.0 | 11 / 8 | |
| 9.1.0 | 11 / 8 | |
| 9.0.0 | 11 / 8 | |
| 8.0.1 | 12 / 8 | |
| 8.0.0 | 12 / 8 | |
| 7.14.0 | 12 / 8 | |
| 7.13.0 | 12 / 8 | |
| 7.12.0 | 12 / 8 | |
| 7.11.3 | 12 / 8 | |
| 7.11.2 | 12 / 8 | |
| 7.11.1 | 12 / 8 | |
| 7.11.0 | 12 / 7 | |
| 7.10.0 | 12 / 7 | |
| 7.9.0 | 12 / 7 | |
| 7.8.0 | 12 / 6 | |
| 7.7.3 | 12 / 6 | |
| 7.7.2 | 12 / 6 | |
| 7.7.1 | 13 / 6 | |
| 7.7.0 | 13 / 6 | |
| 7.6.0 | 13 / 6 | |
| 7.5.0 | 13 / 6 | |
| 7.4.0 | 13 / 6 | |
| 7.3.5 | 13 / 6 | |
| 7.3.4 | 13 / 6 | |
| 7.3.3 | 13 / 6 | |
| 7.3.2 | 13 / 6 | |
| 7.3.1 | 13 / 6 | |
| 7.3.0 | 13 / 6 | |
| 7.2.1 | 13 / 6 | |
| 7.2.0 | 13 / 6 | |
| 7.1.2 | 13 / 6 | |
| 7.1.1 | 13 / 7 | |
| 7.1.0 | 13 / 7 | |
| 7.0.1 | 13 / 7 | |
| 7.0.0 | 13 / 7 | |
| 6.0.1 | 12 / 8 | |
| 6.0.0 | 12 / 8 | |
| 5.0.4 | 12 / 6 | |
| 5.0.3 | 12 / 6 | |
| 5.0.2 | 12 / 6 | |
| 5.0.1 | 12 / 6 | |
| 5.0.0 | 12 / 6 | |
| 4.1.5 | 12 / 6 | |
| 4.1.4 | 13 / 6 | |
| 4.1.3 | 13 / 6 | |
| 4.1.2 | 12 / 6 |
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
v7.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
This version was published by a different npm account than previous versions on 2020-01-14. 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.
v7.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
This version was published by a different npm account than previous versions on 2019-12-22. 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.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.