@tus/file-store
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
acconuttus-botmurderlonuppydev
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance is a legitimate supply chain improvement, not a compromise. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation confirms CI/CD integrity; stable positive signal for this package. | ai | |
| dependencies | unvetted-dep:@tus/utils | AI (dependencies): @tus/utils is a first-party utility from the same tus org; low risk. | ai |
v2.1.0
2 findings
HIGH
Publisher changed: murderlon → GitHub Actions (on 2026-04-21)
provenance
This version was published by a different npm account than previous versions on 2026-04-21. 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.
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.