ctrf
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): ctrf is the Common Test Results Format library (ctrf.io), not a typosquat of cors. Stable false positive. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): glob is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 4 / 14 | |
| 0.1.0 | 5 / 12 | |
| 0.0.17 | 5 / 12 | |
| 0.0.16 | 5 / 12 | |
| 0.0.15 | 3 / 12 | |
| 0.0.14 | 3 / 12 | |
| 0.0.13 | 3 / 12 |
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.