@uppy/tus
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): uppydev is the official Uppy org account; transition from individual maintainer to org account is expected for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): uppydev is the Uppy org account; addition is a legitimate org consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer in favor of org account is consistent with legitimate project governance change. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @uppy/ package from the official uppy monorepo; Levenshtein match to 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @uppy/ package from the official uppy monorepo; Levenshtein match to 'yup' is a false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 3 / 4 | |
| 5.1.0 | 3 / 4 | |
| 5.0.2 | 3 / 4 | |
| 5.0.1 | 3 / 4 | |
| 5.0.0 | 3 / 4 | |
| 3.5.4 | 3 / 1 |
v5.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-09-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-08-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.