@internetarchive/elements
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @internetarchive scoped packages; consistent with org's component library expansion pattern. | ai | |
| dependencies | unvetted-dep:lit | AI (dependencies): lit is the canonical Google/Polymer web components library; well-established and widely trusted in the ecosystem. | ai | |
| dependencies | unvetted-dep:@lit/localize | AI (dependencies): @lit/localize is an official Lit project package for localization; well-established and widely trusted. | ai | |
| dependencies | unvetted-dep:magic-snowflakes | AI (dependencies): magic-snowflakes is a well-known visual effects library with no security concerns; appropriate for a web component library. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.7 | 6 / 23 | |
| 0.2.6 | 6 / 23 | |
| 0.2.5 | 6 / 23 | |
| 0.2.3 | 4 / 23 | |
| 0.2.2 | 4 / 23 | |
| 0.2.1 | 4 / 23 | |
| 0.2.0 | 4 / 23 | |
| 0.1.0 | 4 / 23 | |
| 0.0.1 | 3 / 23 |
v0.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.