@primer/mcp
An MCP server that connects AI tools to the Primer Design System
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from primer-css to GitHub Actions is consistent with CI/CD automation; SLSA attestation confirms legitimate pipeline publish. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @primer/mcp package from GitHub's Primer org; Levenshtein match to 'yup' is coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a runtime peer of @babel/plugin-transform-runtime; conventional indirect usage, not a phantom dep concern. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 8 / 14 | |
| 0.3.1 | 8 / 14 | |
| 0.3.0 | 8 / 14 | |
| 0.2.0 | 8 / 14 | |
| 0.0.5 | 8 / 14 | |
| 0.0.4 | 8 / 14 | |
| 0.0.3 | 8 / 14 | |
| 0.0.2 | 7 / 14 | |
| 0.0.1 | 7 / 14 |
v0.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.