@ray-js/raypack MIT 62 versions

@ray-js/raypack

npm

62

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

tuyafe

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	2026/05/15
phantom-deps	phantom-dep:progress	AI (phantom-deps): Stable false positive for this build tool package.	ai	2026/05/15
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Stable false positive for this build tool package.	ai	2026/05/15
phantom-deps	phantom-dep:resolve-from	AI (phantom-deps): Stable false positive for this build tool package.	ai	2026/05/15
phantom-deps	phantom-dep:esbuild-plugin-less	AI (phantom-deps): Stable false positive for this build tool package.	ai	2026/05/15
phantom-deps	phantom-dep:dedent	AI (phantom-deps): Build tool with many optional/peer deps; phantom-dep heuristic unreliable here.	ai	2026/05/15
phantom-deps	phantom-dep:rimraf	AI (phantom-deps): Used in scripts, not direct imports; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:postcss	AI (phantom-deps): CSS processing dep used indirectly via plugins; stable false positive.	ai	2026/05/15
semgrep	semgrep:new-function-constructor	AI (semgrep): Standard CJS module runner pattern in a build tool; input is controlled build output.	ai	2026/05/15
bogus-package	bogus-package	AI (bogus-package): Monorepo build tool; missing metadata is consistent across the @ray-js package family.	ai	2026/05/15
npm-metadata	no-description	AI (npm-metadata): Consistent with @ray-js monorepo publishing style; not a malware indicator here.	ai	2026/05/15
semgrep	semgrep:dynamic-require	AI (semgrep): Resolves a known framework package path for version checking; not arbitrary module loading.	ai	2026/05/15

Versions (showing 62 of 62)

Version	Deps	Published
1.7.71	33 / 20	2026-06-05
1.7.70	33 / 20	2026-04-29
1.7.69	33 / 20	2026-04-24
1.7.68	33 / 20	2026-04-01
1.7.67	33 / 20	2026-03-31
1.7.66	33 / 20	2026-03-31
1.7.65	33 / 20	2026-03-06
1.7.64	33 / 20	2026-03-05
1.7.63	33 / 20	2026-02-11
1.7.62	33 / 20	2026-02-03
1.7.61	33 / 20	2026-01-30
1.7.60	33 / 20	2026-01-29
1.7.59	33 / 20	2026-01-15
1.7.58	33 / 20	2025-12-12
1.7.57	33 / 20	2025-12-04
1.7.56	33 / 20	2025-11-27
1.7.55	33 / 20	2025-11-11
1.7.54	33 / 20	2025-11-06
1.7.53	33 / 20	2025-11-04
1.7.52	33 / 20	2025-11-03
1.7.51	33 / 20	2025-10-30
1.7.50	33 / 20	2025-10-21
1.7.49	33 / 20	2025-10-21
1.7.48	33 / 20	2025-10-21
1.7.47	33 / 20	2025-10-21
1.7.46	33 / 20	2025-10-20
1.7.45	33 / 20	2025-10-20
1.7.44	33 / 20	2025-10-15
1.7.43	33 / 20	2025-10-13
1.7.42	33 / 20	2025-10-10
1.7.41	33 / 20	2025-09-28
1.7.40	33 / 20	2025-09-25
1.7.39	33 / 20	2025-09-16
1.7.38	33 / 20	2025-09-12
1.7.37	33 / 20	2025-09-08
1.7.36	33 / 20	2025-09-02
1.7.35	33 / 20	2025-09-02
1.7.34	33 / 20	2025-08-21
1.7.33	33 / 20	2025-08-20
1.7.32	33 / 20	2025-08-20
1.7.31	32 / 20	2025-08-18
1.7.30	32 / 20	2025-08-12
1.7.29	32 / 20	2025-08-11
1.7.28	32 / 20	2025-08-08
1.7.27	32 / 20	2025-08-08
1.7.26	32 / 20	2025-08-07
1.7.25	32 / 20	2025-08-04
1.7.24	32 / 20	2025-07-15
1.7.23	32 / 20	2025-07-09
1.7.22	32 / 20	2025-07-08
1.7.21	32 / 20	2025-07-04
1.7.20	32 / 20	2025-07-03
1.7.19	32 / 20	2025-07-03
1.7.18	32 / 20	2025-06-23
1.7.17	32 / 20	2025-06-20
1.7.16	32 / 20	2025-06-17
1.7.15	32 / 20	2025-06-16
1.7.14	32 / 20	2025-06-12
1.7.13	32 / 20	2025-06-10
1.7.12	32 / 20	2025-06-04
1.7.11	32 / 20	2025-05-30
1.7.10	32 / 20	2025-05-08

v1.7.71

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.69

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.67

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.66

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.64

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.63

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.62

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.61

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.60

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.59

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.58

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.57

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.56

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.54

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.53

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.52

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.51

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.49

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.48

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.47

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.45

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.