← Home

toad-cache

npm Repository Homepage
2
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

kibertoad

Keywords

LRUFIFOcacheclientserverleastrecentlyusedfirstbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from manual publish (kibertoad) to GitHub Actions CI/CD with SLSA provenance. ai
provenance missing-githead AI (provenance): gitHead dropped as part of CI/CD migration; SLSA provenance compensates. ai
publish-pattern dormant-publish AI (publish-pattern): Established high-download package; dormancy is normal for stable caches. ai

Versions (showing 2 of 2)

Version Deps Published
3.7.1 0 / 9
3.7.0 0 / 13

v3.7.1

3 findings
HIGH Missing gitHead — previous versions had it provenance

This 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.

HIGH Publisher changed: kibertoad → GitHub Actions (on 2026-05-17) provenance

This version was published by a different npm account than previous versions on 2026-05-17. This could indicate a legitimate maintainer transition or an account compromise.

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.

v3.7.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.