shaclc-write
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@jeswr/prefixcc | AI (dependencies): Same-author dependency (@jeswr namespace); consistent with the package's RDF tooling ecosystem and no malicious indicators. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.6.3 | 3 / 15 | |
| 1.6.2 | 3 / 15 | |
| 1.6.1 | 3 / 15 | |
| 1.6.0 | 3 / 15 | |
| 1.5.0 | 3 / 15 |
v1.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.