@ray-js/lock-sdk MIT 8 versions

@ray-js/lock-sdk

npm

8

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
npm-metadata	no-description	AI (npm-metadata): Consistent pattern across @ray-js/* namespace; not indicative of malice.	ai	2026/05/16
provenance	no-provenance	AI (provenance): No provenance across the @ray-js/* family; stable false positive for this publisher.	ai	2026/05/16
bogus-package	bogus-package	AI (bogus-package): Part of the @ray-js scoped SDK family; missing metadata is typical for internal/scoped packages, not spam.	ai	2026/05/14

Versions (showing 8 of 8)

Version	Deps	Published
1.1.2	2 / 5	2026-05-15
1.1.1	2 / 5	2026-04-28
1.1.0	2 / 5	2026-02-12
1.0.4	2 / 5	2026-01-08
1.0.3	2 / 5	2025-12-01
1.0.2	2 / 5	2025-11-26
1.0.1	2 / 5	2025-11-21
1.0.0	2 / 5	2025-11-20

v1.1.2

1 finding

LOW No provenance attestation provenance

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

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