@warp-drive/utilities
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate org-level CI migration for warp-drive monorepo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known EmberData/WarpDrive org members; consistent with legitimate team expansion. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.8.2 | 1 / 9 | |
| 5.8.1 | 1 / 9 | |
| 5.8.0 | 1 / 9 | |
| 5.7.0 | 1 / 9 | |
| 5.6.0 | 1 / 9 |
v5.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-20. 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.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.