@ray-js/framework-mp
Ray Core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Tuya Ray.js org consistently publishes without Sigstore provenance; stable false positive across all versions. | ai |
Versions (showing 51 of 165)
| Version | Deps | Published |
|---|---|---|
| 1.7.81 | 1 / 0 | |
| 1.7.80 | 1 / 0 | |
| 1.7.79 | 1 / 0 | |
| 1.7.78 | 1 / 0 | |
| 1.7.77 | 1 / 0 | |
| 1.7.76 | 1 / 0 | |
| 1.7.75 | 1 / 0 | |
| 1.7.74 | 1 / 0 | |
| 1.7.73 | 1 / 0 | |
| 1.7.72 | 1 / 0 | |
| 1.7.71 | 1 / 0 | |
| 1.7.70 | 1 / 0 | |
| 1.7.69 | 1 / 0 | |
| 1.7.68 | 1 / 0 | |
| 1.7.67 | 1 / 0 | |
| 1.7.66 | 1 / 0 | |
| 1.7.65 | 1 / 0 | |
| 1.7.64 | 1 / 0 | |
| 1.7.63 | 1 / 0 | |
| 1.7.62 | 1 / 0 | |
| 1.7.61 | 1 / 0 | |
| 1.7.60 | 1 / 0 | |
| 1.7.59 | 1 / 0 | |
| 1.7.58 | 1 / 0 | |
| 1.7.57 | 1 / 0 | |
| 1.7.56 | 1 / 0 | |
| 1.7.55 | 1 / 0 | |
| 1.7.54 | 1 / 0 | |
| 1.7.53 | 1 / 0 | |
| 1.7.52 | 1 / 0 | |
| 1.7.51 | 1 / 0 | |
| 1.7.50 | 1 / 0 | |
| 1.7.49 | 1 / 0 | |
| 1.7.48 | 1 / 0 | |
| 1.7.47 | 1 / 0 | |
| 1.7.46 | 1 / 0 | |
| 1.7.44 | 1 / 0 | |
| 1.7.43 | 1 / 0 | |
| 1.7.42 | 1 / 0 | |
| 1.7.41 | 1 / 0 | |
| 1.7.40 | 1 / 0 | |
| 1.7.39 | 1 / 0 | |
| 1.7.38 | 1 / 0 | |
| 1.7.37 | 1 / 0 | |
| 1.7.36 | 1 / 0 | |
| 1.7.35 | 1 / 0 | |
| 1.7.34 | 1 / 0 | |
| 1.7.33 | 1 / 0 | |
| 1.7.32 | 1 / 0 | |
| 1.7.31 | 1 / 0 | |
| 1.7.30 | 1 / 0 |
v1.7.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.