@ray-js/builder-web
Ray builder for 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 used only in a dev-server console.log display string; not a network request to a raw IP. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): less is a declared runtime dep used via less-loader config; phantom-dep heuristic false positive for this build tool. | ai | |
| phantom-deps | phantom-dep:less-loader | AI (phantom-deps): less-loader referenced in webpack config; stable false positive for this build tool package. | ai | |
| phantom-deps | phantom-dep:slash | AI (phantom-deps): slash used in config path normalization; stable false positive for this build tool package. | ai |
Versions (showing 100 of 166)
| Version | Deps | Published |
|---|---|---|
| 1.7.81 | 26 / 2 | |
| 1.7.80 | 26 / 2 | |
| 1.7.79 | 26 / 2 | |
| 1.7.78 | 26 / 2 | |
| 1.7.77 | 26 / 2 | |
| 1.7.76 | 26 / 2 | |
| 1.7.75 | 26 / 2 | |
| 1.7.74 | 26 / 2 | |
| 1.7.73 | 26 / 2 | |
| 1.7.72 | 26 / 2 | |
| 1.7.71 | 26 / 2 | |
| 1.7.70 | 26 / 2 | |
| 1.7.69 | 26 / 2 | |
| 1.7.68 | 26 / 2 | |
| 1.7.67 | 26 / 2 | |
| 1.7.66 | 26 / 2 | |
| 1.7.65 | 26 / 2 | |
| 1.7.64 | 26 / 2 | |
| 1.7.63 | 26 / 2 | |
| 1.7.62 | 26 / 2 | |
| 1.7.61 | 26 / 2 | |
| 1.7.60 | 26 / 2 | |
| 1.7.59 | 26 / 2 | |
| 1.7.58 | 26 / 2 | |
| 1.7.57 | 26 / 2 | |
| 1.7.56 | 26 / 2 | |
| 1.7.55 | 26 / 2 | |
| 1.7.54 | 26 / 2 | |
| 1.7.53 | 26 / 2 | |
| 1.7.52 | 26 / 2 | |
| 1.7.51 | 26 / 2 | |
| 1.7.50 | 26 / 2 | |
| 1.7.49 | 26 / 2 | |
| 1.7.48 | 26 / 2 | |
| 1.7.47 | 26 / 2 | |
| 1.7.46 | 26 / 2 | |
| 1.7.45 | 26 / 2 | |
| 1.7.44 | 26 / 2 | |
| 1.7.43 | 26 / 2 | |
| 1.7.42 | 26 / 2 | |
| 1.7.41 | 26 / 2 | |
| 1.7.40 | 26 / 2 | |
| 1.7.39 | 26 / 2 | |
| 1.7.38 | 26 / 2 | |
| 1.7.37 | 26 / 2 | |
| 1.7.36 | 26 / 2 | |
| 1.7.35 | 26 / 2 | |
| 1.7.34 | 26 / 2 | |
| 1.7.33 | 26 / 2 | |
| 1.7.32 | 26 / 2 | |
| 1.7.31 | 26 / 2 | |
| 1.7.30 | 26 / 2 | |
| 1.7.29 | 26 / 2 | |
| 1.7.28 | 26 / 2 | |
| 1.7.27 | 26 / 2 | |
| 1.7.26 | 26 / 2 | |
| 1.7.25 | 26 / 2 | |
| 1.7.24 | 26 / 2 | |
| 1.7.23 | 26 / 2 | |
| 1.7.22 | 26 / 2 | |
| 1.7.21 | 26 / 2 | |
| 1.7.20 | 26 / 2 | |
| 1.7.19 | 26 / 2 | |
| 1.7.18 | 26 / 2 | |
| 1.7.17 | 26 / 2 | |
| 1.7.16 | 26 / 2 | |
| 1.7.15 | 26 / 2 | |
| 1.7.14 | 26 / 2 | |
| 1.7.13 | 26 / 2 | |
| 1.7.12 | 26 / 2 | |
| 1.7.11 | 26 / 2 | |
| 1.7.10 | 26 / 2 | |
| 1.7.9 | 26 / 2 | |
| 1.7.8 | 26 / 2 | |
| 1.7.7 | 26 / 2 | |
| 1.7.6 | 26 / 2 | |
| 1.7.5 | 26 / 2 | |
| 1.7.4 | 26 / 2 | |
| 1.7.3 | 26 / 2 | |
| 1.7.2 | 26 / 2 | |
| 1.7.1 | 26 / 2 | |
| 1.7.0 | 26 / 2 | |
| 1.6.32 | 26 / 2 | |
| 1.6.31 | 26 / 2 | |
| 1.6.30 | 26 / 2 | |
| 1.6.29 | 26 / 2 | |
| 1.6.28 | 26 / 2 | |
| 1.6.27 | 26 / 2 | |
| 1.6.26 | 26 / 2 | |
| 1.6.25 | 26 / 2 | |
| 1.6.24 | 26 / 2 | |
| 1.6.23 | 26 / 2 | |
| 1.6.22 | 26 / 2 | |
| 1.6.21 | 26 / 2 | |
| 1.6.20 | 26 / 2 | |
| 1.6.19 | 26 / 2 | |
| 1.6.18 | 26 / 2 | |
| 1.6.17 | 26 / 2 | |
| 1.6.16 | 26 / 2 | |
| 1.6.15 | 26 / 2 |
v1.7.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.