@ray-js/raypack
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:esbuild-plugin-auto-css-modules | AI (phantom-deps): Stable false positive for this build tool package. | ai | |
| phantom-deps | phantom-dep:progress | AI (phantom-deps): Stable false positive for this build tool package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Stable false positive for this build tool package. | ai | |
| phantom-deps | phantom-dep:resolve-from | AI (phantom-deps): Stable false positive for this build tool package. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-less | AI (phantom-deps): Stable false positive for this build tool package. | ai | |
| phantom-deps | phantom-dep:dedent | AI (phantom-deps): Build tool with many optional/peer deps; phantom-dep heuristic unreliable here. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Used in scripts, not direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): CSS processing dep used indirectly via plugins; stable false positive. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard CJS module runner pattern in a build tool; input is controlled build output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo build tool; missing metadata is consistent across the @ray-js package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @ray-js monorepo publishing style; not a malware indicator here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Resolves a known framework package path for version checking; not arbitrary module loading. | ai |
Versions (showing 67 of 167)
| Version | Deps | Published |
|---|---|---|
| 1.6.15 | 28 / 19 | |
| 1.6.14 | 28 / 19 | |
| 1.6.13 | 28 / 19 | |
| 1.6.12 | 27 / 18 | |
| 1.6.11 | 27 / 18 | |
| 1.6.10 | 27 / 18 | |
| 1.6.9 | 27 / 18 | |
| 1.6.8 | 27 / 18 | |
| 1.6.7 | 27 / 18 | |
| 1.6.6 | 27 / 18 | |
| 1.6.5 | 27 / 18 | |
| 1.6.4 | 27 / 18 | |
| 1.6.3 | 27 / 18 | |
| 1.6.2 | 27 / 18 | |
| 1.6.1 | 27 / 18 | |
| 1.6.0 | 27 / 18 | |
| 1.5.48 | 27 / 18 | |
| 1.5.47 | 27 / 18 | |
| 1.5.46 | 27 / 18 | |
| 1.5.45 | 27 / 18 | |
| 1.5.44 | 27 / 18 | |
| 1.5.43 | 26 / 18 | |
| 1.5.42 | 26 / 18 | |
| 1.5.41 | 26 / 18 | |
| 1.5.40 | 26 / 18 | |
| 1.5.39 | 26 / 18 | |
| 1.5.38 | 26 / 18 | |
| 1.5.37 | 26 / 18 | |
| 1.5.36 | 26 / 18 | |
| 1.5.35 | 26 / 18 | |
| 1.5.34 | 26 / 18 | |
| 1.5.33 | 26 / 18 | |
| 1.5.32 | 26 / 18 | |
| 1.5.31 | 26 / 18 | |
| 1.5.30 | 26 / 18 | |
| 1.5.29 | 26 / 18 | |
| 1.5.28 | 26 / 18 | |
| 1.5.27 | 26 / 18 | |
| 1.5.26 | 26 / 18 | |
| 1.5.25 | 26 / 18 | |
| 1.5.24 | 26 / 18 | |
| 1.5.23 | 26 / 18 | |
| 1.5.22 | 26 / 18 | |
| 1.5.21 | 26 / 18 | |
| 1.5.20 | 26 / 18 | |
| 1.5.19 | 25 / 18 | |
| 1.5.18 | 25 / 18 | |
| 1.5.17 | 25 / 18 | |
| 1.5.16 | 25 / 18 | |
| 1.5.15 | 25 / 18 | |
| 1.5.14 | 25 / 18 | |
| 1.5.13 | 25 / 18 | |
| 1.5.12 | 25 / 18 | |
| 1.5.11 | 25 / 18 | |
| 1.5.10 | 25 / 18 | |
| 1.5.9 | 25 / 18 | |
| 1.5.8 | 25 / 18 | |
| 1.5.7 | 25 / 18 | |
| 1.5.6 | 25 / 18 | |
| 1.5.5 | 25 / 18 | |
| 1.5.4 | 25 / 18 | |
| 1.5.3 | 25 / 18 | |
| 1.5.2 | 25 / 18 | |
| 1.5.1 | 25 / 18 | |
| 1.5.0 | 25 / 18 | |
| 1.4.63 | 25 / 18 | |
| 1.4.62 | 25 / 18 |
v1.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.