@rocicorp/lock
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; gitHead absence is a minor metadata gap, not a supply chain risk. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI/CD pipeline with SLSA attestation explains rapid successive publish; not indicative of malicious activity. | ai | |
| provenance | publisher-changed | AI (provenance): Rocicorp migrated publishing to GitHub Actions CI with SLSA attestation; this is a documented org-level practice. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable utility package; long gap between v1 and v2 is consistent with low-churn maintenance, not takeover. | ai |
v2.0.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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.