← Home

@internetarchive/feature-feedback

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

bfallingmitraardronvbanoskngenieiisacdrininsharma123dualcnhqlatonvibnesayeedtracey.poohjim-at-iajeffwkleinrebecca-shoptawjbuckner

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:lit AI (dependencies): lit is Google's official web components library; widely used and trusted across the ecosystem. ai
dependencies unvetted-dep:@lit/localize AI (dependencies): @lit/localize is the official Lit localization package from Google; well-known and trusted. ai
dependencies unvetted-dep:@internetarchive/ia-styles AI (dependencies): Same-org @internetarchive scoped package; consistent with Internet Archive's ecosystem. ai
dependencies unvetted-dep:@internetarchive/result-type AI (dependencies): Same-org @internetarchive scoped package; consistent with Internet Archive's ecosystem. ai
dependencies unvetted-dep:@internetarchive/recaptcha-manager AI (dependencies): Same-org @internetarchive scoped package; consistent with Internet Archive's ecosystem. ai
dependencies unvetted-dep:@internetarchive/shared-resize-observer AI (dependencies): Same-org @internetarchive scoped package; consistent with Internet Archive's ecosystem. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.1 6 / 20
1.1.0 6 / 20
1.0.0 4 / 18

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.