@ray-js/build-plugin-router
Ray build plugin for router
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of Tuya/Ray.js monorepo; sparse README and missing repo URL are consistent across the entire package family. | ai | |
| provenance | no-provenance | AI (provenance): Tuya publishes 500+ versions without provenance; stable pattern for this publisher. | ai |
Versions (showing 100 of 166)
| Version | Deps | Published |
|---|---|---|
| 1.7.82 | 7 / 1 | |
| 1.7.81 | 7 / 1 | |
| 1.7.80 | 7 / 1 | |
| 1.7.79 | 7 / 1 | |
| 1.7.78 | 7 / 1 | |
| 1.7.77 | 7 / 1 | |
| 1.7.76 | 7 / 1 | |
| 1.7.75 | 7 / 1 | |
| 1.7.74 | 7 / 1 | |
| 1.7.73 | 7 / 1 | |
| 1.7.72 | 7 / 1 | |
| 1.7.71 | 7 / 1 | |
| 1.7.70 | 7 / 1 | |
| 1.7.69 | 7 / 1 | |
| 1.7.68 | 7 / 1 | |
| 1.7.67 | 7 / 1 | |
| 1.7.66 | 7 / 1 | |
| 1.7.65 | 7 / 1 | |
| 1.7.64 | 7 / 1 | |
| 1.7.63 | 7 / 1 | |
| 1.7.62 | 7 / 1 | |
| 1.7.61 | 7 / 1 | |
| 1.7.60 | 7 / 1 | |
| 1.7.59 | 7 / 1 | |
| 1.7.58 | 7 / 1 | |
| 1.7.57 | 7 / 1 | |
| 1.7.56 | 7 / 1 | |
| 1.7.55 | 7 / 1 | |
| 1.7.54 | 7 / 1 | |
| 1.7.53 | 7 / 1 | |
| 1.7.52 | 7 / 1 | |
| 1.7.51 | 7 / 1 | |
| 1.7.50 | 7 / 1 | |
| 1.7.49 | 7 / 1 | |
| 1.7.48 | 7 / 1 | |
| 1.7.47 | 7 / 1 | |
| 1.7.46 | 7 / 1 | |
| 1.7.44 | 7 / 1 | |
| 1.7.43 | 7 / 1 | |
| 1.7.42 | 7 / 1 | |
| 1.7.41 | 7 / 1 | |
| 1.7.40 | 7 / 1 | |
| 1.7.39 | 7 / 1 | |
| 1.7.38 | 7 / 1 | |
| 1.7.37 | 7 / 1 | |
| 1.7.36 | 7 / 1 | |
| 1.7.35 | 7 / 1 | |
| 1.7.34 | 7 / 1 | |
| 1.7.33 | 7 / 1 | |
| 1.7.32 | 7 / 1 | |
| 1.7.31 | 7 / 1 | |
| 1.7.30 | 7 / 1 | |
| 1.7.29 | 7 / 1 | |
| 1.7.28 | 7 / 1 | |
| 1.7.27 | 7 / 1 | |
| 1.7.26 | 7 / 1 | |
| 1.7.25 | 7 / 1 | |
| 1.7.24 | 7 / 1 | |
| 1.7.23 | 7 / 1 | |
| 1.7.22 | 7 / 1 | |
| 1.7.21 | 7 / 1 | |
| 1.7.20 | 7 / 1 | |
| 1.7.19 | 7 / 1 | |
| 1.7.18 | 7 / 1 | |
| 1.7.17 | 7 / 1 | |
| 1.7.16 | 7 / 1 | |
| 1.7.15 | 7 / 1 | |
| 1.7.14 | 7 / 1 | |
| 1.7.13 | 7 / 1 | |
| 1.7.12 | 7 / 1 | |
| 1.7.11 | 7 / 1 | |
| 1.7.10 | 7 / 1 | |
| 1.7.9 | 7 / 1 | |
| 1.7.8 | 7 / 1 | |
| 1.7.7 | 7 / 1 | |
| 1.7.6 | 7 / 1 | |
| 1.7.5 | 7 / 1 | |
| 1.7.4 | 7 / 1 | |
| 1.7.3 | 7 / 1 | |
| 1.7.2 | 7 / 1 | |
| 1.7.1 | 7 / 1 | |
| 1.7.0 | 7 / 1 | |
| 1.6.32 | 7 / 1 | |
| 1.6.31 | 7 / 1 | |
| 1.6.30 | 7 / 1 | |
| 1.6.29 | 7 / 1 | |
| 1.6.28 | 7 / 1 | |
| 1.6.27 | 7 / 1 | |
| 1.6.26 | 7 / 1 | |
| 1.6.25 | 7 / 1 | |
| 1.6.24 | 7 / 1 | |
| 1.6.23 | 7 / 1 | |
| 1.6.22 | 7 / 1 | |
| 1.6.21 | 7 / 1 | |
| 1.6.20 | 7 / 1 | |
| 1.6.19 | 7 / 1 | |
| 1.6.18 | 7 / 1 | |
| 1.6.17 | 7 / 1 | |
| 1.6.16 | 7 / 1 | |
| 1.6.15 | 7 / 1 |
v1.7.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.