← Home

@uiid/code

npm Repository Homepage

Code highlighting components powered by Shiki

14
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

adamfratino

Keywords

uiidreactcomponentsdesign-systemcodesyntax-highlightingshiki

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @uiid org package; not a typosquat of cors — name similarity is coincidental. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @uiid org package; not a typosquat of zod — name similarity is coincidental. ai
phantom-deps phantom-dep:@uiid/cards AI (phantom-deps): Same-org sibling dep; may be used indirectly or re-exported in the design system monorepo. ai
phantom-deps phantom-dep:@uiid/tokens AI (phantom-deps): Same-org sibling dep; likely used via CSS/design tokens rather than direct JS import. ai

Versions (showing 14 of 14)

Version Deps Published
0.0.22 10 / 26
0.0.21 10 / 26
0.0.20 9 / 26
0.0.19 9 / 26
0.0.18 9 / 28
0.0.17 9 / 28
0.0.16 9 / 28
0.0.15 9 / 28
0.0.14 9 / 28
0.0.12 9 / 28
0.0.11 9 / 28
0.0.10 9 / 28
0.0.8 9 / 28
0.0.7 9 / 28

v0.0.22

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

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.

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

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.

v0.0.17

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.

v0.0.16

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.

v0.0.15

1 finding
LOW No provenance attestation provenance

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

v0.0.14

1 finding
LOW No provenance attestation provenance

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

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.8

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.

v0.0.7

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.