← Home

@uiid/registry

npm Repository Homepage

Component metadata, Zod schemas, and AI-friendly documentation

27
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

adamfratino

Keywords

uiidreactcomponentsdesign-systemregistryschemaszod

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): New package; provenance absence is common and no other risk signals present. ai

Versions (showing 27 of 27)

Version Deps Published
0.0.36 2 / 10
0.0.35 2 / 10
0.0.34 2 / 10
0.0.33 2 / 10
0.0.32 2 / 10
0.0.31 2 / 10
0.0.30 2 / 10
0.0.29 2 / 10
0.0.28 2 / 10
0.0.27 2 / 10
0.0.26 2 / 10
0.0.25 2 / 10
0.0.23 2 / 10
0.0.22 2 / 10
0.0.21 2 / 10
0.0.20 2 / 10
0.0.19 2 / 10
0.0.18 2 / 10
0.0.17 2 / 10
0.0.16 2 / 10
0.0.15 2 / 10
0.0.14 2 / 10
0.0.12 2 / 10
0.0.11 2 / 10
0.0.10 2 / 10
0.0.8 2 / 10
0.0.7 2 / 10

v0.0.36

1 finding
INFO No provenance attestation provenance

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

v0.0.35

1 finding
INFO No provenance attestation provenance

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

v0.0.34

1 finding
INFO No provenance attestation provenance

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

v0.0.33

1 finding
INFO No provenance attestation provenance

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

v0.0.32

1 finding
INFO No provenance attestation provenance

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

v0.0.31

1 finding
INFO No provenance attestation provenance

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

v0.0.30

1 finding
INFO No provenance attestation provenance

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

v0.0.29

1 finding
INFO No provenance attestation provenance

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

v0.0.28

1 finding
INFO No provenance attestation provenance

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

v0.0.27

1 finding
INFO No provenance attestation provenance

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