@uppy/vue
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped @uppy/* package; Levenshtein match against 'vite' is a false positive for this well-known uploader library. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @uppy/* package; Levenshtein match against 'yup' is a false positive for this well-known uploader library. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package in the Uppy ecosystem; missing metadata fields are a style issue, not a spam indicator. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 3 / 3 | |
| 3.1.0 | 3 / 3 | |
| 3.0.3 | 3 / 3 | |
| 3.0.2 | 3 / 3 | |
| 3.0.1 | 3 / 3 | |
| 3.0.0 | 3 / 3 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.