@bonhomie/cloudinary-super-uploader
A powerful React + Node Cloudinary toolkit with drag & drop, browser compression, EXIF checks, duplicate detection, signed uploads, and more.
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 | no-provenance | AI (provenance): Small scoped package; lack of provenance is common and no other risk signals present. | ai | |
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): sharp is a declared runtime dep used as a native binding; phantom-dep heuristic fires because it's not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:cloudinary | AI (phantom-deps): cloudinary is a declared runtime dep; phantom-dep fires due to indirect/config-based usage pattern. | ai | |
| phantom-deps | phantom-dep:image-hash | AI (phantom-deps): image-hash is a declared runtime dep; phantom-dep fires due to indirect/config-based usage pattern. | ai | |
| phantom-deps | phantom-dep:exif-parser | AI (phantom-deps): exif-parser is a declared runtime dep; phantom-dep fires due to indirect/config-based usage pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 1 / 2 | |
| 2.0.1 | 4 / 2 | |
| 1.0.4 | 5 / 2 | |
| 1.0.3 | 4 / 2 | |
| 1.0.2 | 4 / 2 | |
| 1.0.1 | 4 / 2 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.