@eui/mcp
MCP server for EUI Angular component library using Compodoc documentation
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Marked external in esbuild; used at runtime, not imported in source. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Marked external in esbuild; used at runtime, not imported in source. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): Marked external in esbuild; used at runtime, not imported in source. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Marked external in esbuild; used at runtime, not imported in source. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Marked external in esbuild; core runtime dependency for MCP server. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped Angular MCP server package; name similarity to 'yup' is coincidental, not a typosquat. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 21.2.6 | 0 / 0 | |
| 21.2.5 | 0 / 0 | |
| 21.2.4 | 0 / 0 | |
| 1.5.10 | 5 / 13 | |
| 1.5.8 | 5 / 13 | |
| 1.5.7 | 5 / 13 | |
| 1.5.6 | 5 / 13 | |
| 1.5.5 | 5 / 13 | |
| 1.5.4 | 5 / 13 | |
| 1.5.3 | 5 / 13 | |
| 1.5.2 | 5 / 13 | |
| 1.5.1 | 5 / 12 | |
| 1.5.0 | 3 / 12 | |
| 1.4.0 | 3 / 12 | |
| 1.3.0 | 3 / 12 | |
| 1.2.0 | 3 / 12 | |
| 1.0.3 | 3 / 12 |
v21.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.