@ray-core/web
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
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 7 / 7 | |
| 0.4.14 | 7 / 7 | |
| 0.4.13 | 7 / 7 | |
| 0.4.12 | 7 / 7 | |
| 0.4.11 | 7 / 7 | |
| 0.4.10 | 7 / 7 | |
| 0.4.9 | 7 / 7 | |
| 0.4.8 | 7 / 7 | |
| 0.4.7 | 7 / 7 | |
| 0.4.6 | 7 / 7 |
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.