← Home

@ray-js/smart-ui

npm

轻量、可靠的智能小程序 UI 组件库

41
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-js/smart-uiraysmart-uiweapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 41 of 41)

Version Deps Published
2.13.2 3 / 28
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
2.3.7 3 / 28
2.3.6 3 / 28
2.3.5 3 / 28
2.3.3 3 / 28
2.3.2 3 / 28
2.3.0 3 / 28
2.2.1 3 / 28
2.2.0 3 / 28
2.1.10 3 / 28
2.1.8 3 / 28
2.1.7 3 / 28
2.1.6 3 / 28
2.1.5 5 / 28
2.1.4 5 / 28
2.1.1 5 / 29
2.1.0 5 / 29
2.0.0 5 / 29

v2.3.7

1 finding
INFO No provenance attestation provenance

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

v2.3.6

1 finding
INFO No provenance attestation provenance

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

v2.3.5

1 finding
INFO No provenance attestation provenance

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

v2.3.3

1 finding
INFO No provenance attestation provenance

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

v2.3.2

1 finding
INFO No provenance attestation provenance

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

v2.3.0

1 finding
INFO No provenance attestation provenance

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

v2.2.1

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.10

1 finding
INFO No provenance attestation provenance

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

v2.1.8

1 finding
INFO No provenance attestation provenance

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

v2.1.7

1 finding
INFO No provenance attestation provenance

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

v2.1.6

1 finding
INFO No provenance attestation provenance

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

v2.1.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.4

1 finding
INFO No provenance attestation provenance

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

v2.1.1

1 finding
INFO No provenance attestation provenance

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

v2.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.