← Home

@uiid/mcp

npm Repository Homepage

MCP server exposing UIID component metadata and blocks to LLMs

13
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

uiidmcpdesign-systemaillmcomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @uiid/mcp is unrelated to yup; Levenshtein match is coincidental. ai
phantom-deps phantom-dep:@uiid/blocks AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@uiid/registry AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo packages. ai

Versions (showing 13 of 13)

Version Deps Published
0.0.15 4 / 2
0.0.14 4 / 2
0.0.13 4 / 2
0.0.12 4 / 2
0.0.11 4 / 2
0.0.10 4 / 2
0.0.9 4 / 2
0.0.8 4 / 2
0.0.7 4 / 2
0.0.5 4 / 2
0.0.4 4 / 2
0.0.3 4 / 2
0.0.2 4 / 2

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

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

v0.0.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.

v0.0.10

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

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

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

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

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.