← Home

@ray-js/api

npm

Ray universal api

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
bogus-package bogus-package AI (bogus-package): Scoped framework package; sparse README and empty repo object are normal for internal monorepo components. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped Tuya/Ray ecosystem package; not a typosquat of pg. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped Tuya/Ray ecosystem package; not a typosquat of joi. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped Tuya/Ray ecosystem package; not a typosquat of ajv. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped Tuya/Ray ecosystem package; not a typosquat of hapi. ai
dependencies unvetted-dep:@ray-js/framework AI (dependencies): Sibling monorepo package at matching version; stable pattern across releases. ai
dependencies unvetted-dep:base64-browser AI (dependencies): Small utility dep with no known advisories; consistent across versions. ai
dependencies unvetted-dep:@ray-js/router AI (dependencies): Sibling monorepo package at matching version; stable pattern across releases. ai

Versions (showing 100 of 162)

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

1 finding
LOW No provenance attestation provenance

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

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.

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