@ray-js/icons MIT 25 versions

@ray-js/icons

npm

Ray basic components

25

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

Keywords

ray

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:hooks	AI (dependencies): Declared but phantom (not directly imported); stable config-only reference across this package's versions.	ai	2026/05/15
dependencies	unvetted-dep:@ray-core/macro	AI (dependencies): Same org ecosystem dependency; consistent across Ray framework packages.	ai	2026/05/15
dependencies	unvetted-dep:@ray-core/wechat	AI (dependencies): Same org ecosystem dependency; consistent across Ray framework packages.	ai	2026/05/15
provenance	no-provenance	AI (provenance): Tuya org package with long publish history; provenance not used by this publisher across versions.	ai	2026/05/15
phantom-deps	phantom-dep:core-js	AI (phantom-deps): Known implicit runtime polyfill dependency; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:param-case	AI (phantom-deps): Referenced in config files; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:@ray-core/macro	AI (phantom-deps): Internal monorepo dep used in build config; stable false positive.	ai	2026/05/15
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped icon library from Tuya org; Levenshtein match to 'cors' is coincidental and not a squatting attempt.	ai	2026/05/15
phantom-deps	phantom-dep:style-to-object	AI (phantom-deps): Referenced in config files; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:@ray-core/wechat	AI (phantom-deps): Internal monorepo dep used in build config; stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:@ray-js/framework-shared	AI (phantom-deps): Same org scope; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:@ray-js/adapter	AI (phantom-deps): Same org scope; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:clsx	AI (phantom-deps): Declared dependency in a component library; likely used in build output or config, stable false positive.	ai	2026/05/15
phantom-deps	phantom-dep:hooks	AI (phantom-deps): Referenced in config files; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:ahooks	AI (phantom-deps): Referenced in config files; stable false positive for this package.	ai	2026/05/15

Versions (showing 25 of 25)

Version	Deps	Published
1.7.70	11 / 1	2026-04-29
1.7.69	11 / 1	2026-04-24
1.7.68	11 / 1	2026-04-01
1.7.66	11 / 1	2026-03-31
1.7.63	11 / 1	2026-02-11
1.7.62	11 / 1	2026-02-03
1.7.59	11 / 1	2026-01-15
1.7.56	11 / 1	2025-11-27
1.7.55	11 / 1	2025-11-11
1.7.52	11 / 1	2025-11-03
1.7.47	11 / 1	2025-10-21
1.7.41	11 / 1	2025-09-28
1.7.40	11 / 1	2025-09-25
1.7.36	11 / 1	2025-09-02
1.7.34	11 / 1	2025-08-21
1.7.33	11 / 1	2025-08-20
1.7.32	11 / 1	2025-08-20
1.7.29	11 / 1	2025-08-11
1.7.24	11 / 1	2025-07-15
1.7.23	11 / 1	2025-07-09
1.7.19	11 / 1	2025-07-03
1.7.14	11 / 1	2025-06-12
1.7.13	11 / 1	2025-06-10
1.7.12	11 / 1	2025-06-04
1.7.11	11 / 1	2025-05-30

v1.7.70

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.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.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.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. 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. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.56

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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.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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.24

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.7.13

1 finding

LOW No provenance attestation provenance

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

v1.7.12

1 finding

LOW No provenance attestation provenance

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

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.