@panneau/uppy
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): dmongeau is a named contributor (David Mongeau-Petitpas) in package.json; legitimate org maintainer, 311 approved packages. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance absence is a best-practice gap, not a security blocker. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; description field is empty but metadata is otherwise complete and legitimate. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel runtime loaded by convention; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@uppy/facebook | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/dashboard | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/transloadit | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/google-drive | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/instagram | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/webcam | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/dropbox | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@uppy/locales | AI (dependencies): Official @uppy scoped package from transloadit; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@uppy/react | AI (phantom-deps): Build-time/config reference in a monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@uppy/dashboard | AI (phantom-deps): Build-time/config reference in a monorepo; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.0.55 | 18 / 2 | |
| 4.0.50 | 18 / 2 | |
| 4.0.48 | 18 / 2 | |
| 4.0.41 | 18 / 2 | |
| 4.0.38 | 18 / 2 | |
| 4.0.37 | 18 / 2 | |
| 4.0.27 | 18 / 2 | |
| 4.0.15 | 18 / 2 | |
| 4.0.11 | 19 / 2 | |
| 4.0.7 | 19 / 2 | |
| 4.0.5 | 19 / 2 | |
| 4.0.4 | 19 / 2 | |
| 4.0.2 | 19 / 2 | |
| 4.0.1 | 19 / 2 | |
| 4.0.0 | 19 / 2 | |
| 3.0.317 | 19 / 2 | |
| 3.0.314 | 19 / 2 | |
| 3.0.307 | 19 / 2 |
v4.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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.
v4.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.317
2 findingsThis version was published by a different npm account than previous versions on 2025-12-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.
v3.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.