@codecov/bundler-plugin-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Base64 llhttp WASM from bundled undici, not a payload. | ai | |
| source-diff | encoded-string-file:dist/index.mjs | AI (source-diff): Same WASM blob in ESM build output. | ai | |
| phantom-deps | phantom-dep:@actions/core | AI (phantom-deps): Used in CI config, stable FP. | ai | |
| phantom-deps | phantom-dep:@actions/github | AI (phantom-deps): Used in CI config, stable FP. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 6 / 14 | |
| 2.0.0 | 6 / 14 | |
| 1.9.1 | 6 / 14 | |
| 1.9.0 | 6 / 14 |
v2.0.0
4 findingsThis version was published by a different npm account than previous versions on 2026-04-14. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.