@equinor/eds-utils
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): Equinor migrated publishing to GitHub Actions CI with SLSA attestation; legitimate pipeline change for this org. | ai | |
| provenance | missing-githead | AI (provenance): CI/CD pipeline change explains missing gitHead; SLSA provenance attestation provides stronger commit linkage. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Runtime Babel helper dep; loaded by convention via Babel transform, not direct import. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 2 / 28 | |
| 2.2.0 | 2 / 28 | |
| 2.1.0 | 2 / 28 | |
| 2.0.0 | 2 / 28 |
v2.2.1
3 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.
This version was published by a different npm account than previous versions on 2026-05-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.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.