@ray-js/smart-ui
轻量、可靠的智能小程序 UI 组件库
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tuya-miniapp/smart-ui | AI (dependencies): First-party Tuya dependency; core upstream for this wrapper package across all versions. | ai | |
| dependencies | unvetted-dep:@ray-js/components-ty-slider | AI (dependencies): First-party Ray/Tuya component dep; consistent with package's UI library purpose. | ai | |
| provenance | no-provenance | AI (provenance): Tuya org packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.13.1 | 3 / 28 | |
| 2.13.0 | 3 / 28 | |
| 2.12.0 | 3 / 28 | |
| 2.11.1 | 3 / 28 | |
| 2.11.0 | 3 / 28 | |
| 2.10.0 | 3 / 28 | |
| 2.9.2 | 3 / 28 | |
| 2.9.1 | 3 / 28 | |
| 2.9.0 | 3 / 28 | |
| 2.8.0 | 3 / 28 | |
| 2.7.3 | 3 / 28 | |
| 2.7.2 | 3 / 28 | |
| 2.7.1 | 3 / 28 | |
| 2.7.0 | 3 / 28 | |
| 2.6.3 | 3 / 28 | |
| 2.6.2 | 3 / 28 | |
| 2.6.1 | 3 / 28 | |
| 2.6.0 | 3 / 28 | |
| 2.5.1 | 4 / 28 | |
| 2.5.0 | 3 / 28 | |
| 2.4.0 | 3 / 28 | |
| 2.3.9 | 3 / 28 | |
| 2.3.8 | 3 / 28 |
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.