@igniteui/mcp-server
Unified MCP server for Ignite UI — documentation, GitHub API, and CLI scaffolding
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate @igniteui-scoped MCP server; missing metadata is a gap but not a spam/malware indicator for this publisher. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 15.2.2 | 4 / 14 | |
| 15.2.1 | 4 / 14 | |
| 15.2.0 | 4 / 14 | |
| 15.1.0 | 4 / 14 | |
| 15.0.1 | 4 / 14 | |
| 15.0.0 | 4 / 14 |
v15.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.