← Home

@ray-js/cli

npm

Ray cli

100
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tuyafe

Keywords

ray

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @ray-js/cli is a Tuya framework CLI; Levenshtein match to 'joi' is a false positive. ai
phantom-deps phantom-dep:@ray-js/types AI (phantom-deps): Same-org type-only dep; not directly imported by design. ai
phantom-deps phantom-dep:webpack-chain AI (phantom-deps): Referenced in config files; stable false positive for this package. ai
phantom-deps phantom-dep:@ray-js/build-plugin-ray AI (phantom-deps): Same-org dep passed through to consumers; stable false positive. ai
phantom-deps phantom-dep:@ray-js/build-plugin-router AI (phantom-deps): Same-org dep passed through to consumers; stable false positive. ai

Versions (showing 100 of 166)

Version Deps Published
1.7.82 11 / 4
1.7.81 11 / 4
1.7.80 11 / 4
1.7.79 11 / 4
1.7.78 11 / 4
1.7.77 11 / 4
1.7.76 11 / 4
1.7.75 11 / 4
1.7.74 11 / 4
1.7.73 11 / 4
1.7.72 11 / 4
1.7.71 11 / 4
1.7.70 11 / 4
1.7.69 11 / 4
1.7.68 11 / 4
1.7.67 11 / 4
1.7.66 11 / 4
1.7.65 11 / 4
1.7.64 11 / 4
1.7.63 11 / 4
1.7.62 11 / 4
1.7.61 11 / 4
1.7.60 11 / 4
1.7.59 11 / 4
1.7.58 11 / 4
1.7.57 11 / 4
1.7.56 11 / 4
1.7.55 11 / 4
1.7.54 11 / 4
1.7.53 11 / 4
1.7.52 11 / 4
1.7.51 11 / 4
1.7.50 11 / 4
1.7.49 11 / 4
1.7.48 11 / 4
1.7.47 11 / 4
1.7.46 11 / 4
1.7.44 11 / 4
1.7.43 11 / 4
1.7.42 11 / 4
1.7.41 11 / 4
1.7.40 11 / 4
1.7.39 11 / 4
1.7.38 11 / 4
1.7.37 11 / 4
1.7.36 11 / 4
1.7.35 11 / 4
1.7.34 11 / 4
1.7.33 11 / 4
1.7.32 11 / 4
1.7.31 11 / 4
1.7.30 11 / 4
1.7.29 11 / 4
1.7.28 11 / 4
1.7.27 11 / 4
1.7.26 11 / 4
1.7.25 11 / 4
1.7.24 11 / 4
1.7.23 11 / 4
1.7.22 11 / 4
1.7.21 11 / 4
1.7.20 11 / 4
1.7.19 11 / 4
1.7.18 11 / 4
1.7.17 11 / 4
1.7.16 11 / 4
1.7.15 11 / 4
1.7.14 11 / 4
1.7.13 11 / 4
1.7.12 11 / 4
1.7.11 11 / 4
1.7.10 11 / 4
1.7.9 11 / 4
1.7.8 11 / 4
1.7.7 11 / 4
1.7.6 11 / 4
1.7.5 11 / 4
1.7.4 11 / 4
1.7.3 11 / 4
1.7.2 11 / 4
1.7.1 11 / 4
1.7.0 11 / 4
1.6.32 11 / 4
1.6.31 11 / 4
1.6.30 11 / 4
1.6.29 11 / 4
1.6.28 11 / 4
1.6.27 11 / 4
1.6.26 11 / 4
1.6.25 11 / 1
1.6.24 11 / 1
1.6.23 11 / 1
1.6.22 11 / 1
1.6.21 11 / 1
1.6.20 11 / 1
1.6.19 11 / 1
1.6.18 11 / 1
1.6.17 11 / 1
1.6.16 11 / 1
1.6.15 11 / 1
Showing 100 of 166 Next page →

v1.7.82

1 finding
LOW No provenance attestation provenance

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

v1.7.81

1 finding
LOW No provenance attestation provenance

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

v1.7.80

1 finding
LOW No provenance attestation provenance

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

v1.7.79

1 finding
LOW No provenance attestation provenance

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

v1.7.78

1 finding
LOW No provenance attestation provenance

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

v1.7.77

1 finding
LOW No provenance attestation provenance

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

v1.7.76

1 finding
LOW No provenance attestation provenance

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

v1.7.9

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.8

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.7

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.6

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.5

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.4

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.3

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.2

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.1

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.0

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.6.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.6.31

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.6.30

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.6.29

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.6.28

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.6.27

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.6.26

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.6.25

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.6.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.6.23

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.6.22

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.6.21

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.6.20

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.6.19

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.6.18

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.6.17

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.6.16

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.6.15

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.