@cypress/code-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:@cypress/code-coverage | AI (npm-metadata): Self-referential file:. devDependency for local testing, not a supply-chain risk. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 9 / 31 | |
| 4.0.2 | 9 / 31 | |
| 4.0.1 | 9 / 31 | |
| 4.0.0 | 9 / 31 |
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.