@uppy/components
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@uppy/audio | AI (phantom-deps): Same-org @uppy/* dep; likely re-exported from package rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@uppy/image-editor | AI (phantom-deps): Same-org @uppy/* dep; likely re-exported from package rather than directly imported in source. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 4 / 7 | |
| 1.1.0 | 4 / 4 | |
| 1.0.4 | 10 / 3 | |
| 1.0.3 | 10 / 3 | |
| 1.0.2 | 10 / 3 | |
| 1.0.1 | 10 / 3 | |
| 1.0.0 | 10 / 3 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.