@cloudinary/react
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cloudinary/html | AI (dependencies): First-party Cloudinary monorepo package; stable dependency across all versions of this SDK. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.14.4 | 1 / 46 | |
| 1.14.3 | 1 / 46 | |
| 1.14.2 | 1 / 46 | |
| 1.14.1 | 1 / 46 | |
| 1.14.0 | 1 / 46 | |
| 1.13.1 | 1 / 46 |
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.