@uppy/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @uppy/core is the canonical Uppy core package from Transloadit, not a typosquat of 'cors'. | ai | |
| dependencies | unvetted-dep:@uppy/utils | AI (dependencies): First-party @uppy scoped package from the same Transloadit monorepo. | ai | |
| dependencies | unvetted-dep:@uppy/store-default | AI (dependencies): First-party @uppy scoped package from the same Transloadit monorepo. | ai | |
| dependencies | unvetted-dep:@transloadit/prettier-bytes | AI (dependencies): First-party @transloadit scoped package from the same org. | ai | |
| dependencies | unvetted-dep:namespace-emitter | AI (dependencies): Small, stable event emitter utility; long-standing dependency of Uppy. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 8 / 9 | |
| 5.1.1 | 8 / 9 | |
| 5.1.0 | 8 / 9 | |
| 5.0.2 | 8 / 9 | |
| 5.0.1 | 8 / 9 | |
| 5.0.0 | 8 / 9 |
v5.2.0
2 findingsPackage name '@uppy/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.