← Home

@web-widget/shared-cache

npm Repository Homepage
14
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

aui

Keywords

cachehttp-cacheweb-cache-apifetchserver-sideshared-cacherfc-7234rfc-5861stale-while-revalidatestale-if-errornodedenobunwintercgredislrucache-controlvarytypescriptcross-runtime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; consistent with CI/CD automation of an established package. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI-attested publish with no code changes; low-risk resumption of maintenance. ai
provenance no-provenance AI (provenance): Established package with consistent publishing history; lack of provenance is common and not a risk signal here. ai

Versions (showing 14 of 14)

Version Deps Published
2.1.0 2 / 22
2.0.0 2 / 22
1.9.0 2 / 22
1.8.0 2 / 22
1.7.2 2 / 22
1.7.1 2 / 22
1.7.0 2 / 22
1.6.0 2 / 22
1.5.0 2 / 22
1.4.0 2 / 22
1.3.0 2 / 22
1.2.0 2 / 22
1.1.0 2 / 22
1.0.0 2 / 22

v2.1.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
INFO No provenance attestation provenance

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