react-easy-crop
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.5.7 | 2 / 0 | |
| 5.5.6 | 2 / 0 | |
| 5.5.5 | 2 / 0 | |
| 5.5.4 | 2 / 0 | |
| 5.5.3 | 2 / 0 | |
| 5.5.2 | 2 / 0 | |
| 5.5.1 | 2 / 0 | |
| 5.5.0 | 2 / 0 | |
| 5.4.2 | 2 / 0 |
v5.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.