@vuetify/mcp
Model Context Protocol server for Vuetify assistance
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Vuetify org migrated to GitHub Actions publishing with SLSA attestation; this is expected for the vuetifyjs org. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): CLI tool copies process.env to pass to subprocess; standard pattern, not exfiltration. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @vuetify/ package from official vuetifyjs org; no relation to 'yup'. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 13 / 10 | |
| 0.5.0 | 13 / 10 | |
| 0.4.6 | 13 / 10 | |
| 0.4.5 | 13 / 10 | |
| 0.4.4 | 13 / 10 | |
| 0.4.1 | 13 / 10 | |
| 0.4.0 | 13 / 10 | |
| 0.3.0 | 13 / 10 | |
| 0.2.4 | 13 / 10 | |
| 0.2.3 | 13 / 11 | |
| 0.2.2 | 13 / 11 | |
| 0.2.1 | 13 / 11 | |
| 0.2.0 | 13 / 11 | |
| 0.1.1 | 13 / 9 | |
| 0.1.0 | 13 / 9 | |
| 0.0.6 | 4 / 13 | |
| 0.0.5 | 4 / 10 | |
| 0.0.4 | 4 / 10 | |
| 0.0.2 | 4 / 9 |
v0.7.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/vuetifyjs/mcp/blob/1a025dacd39daaa51a2927d61962ee58f4a83a84/bin/cli.js#L11 9 | 10 | function setupEnvironment (args) { > 11 | const env = { ...process.env } 12 | if (args['api-key']) { 13 | env.VUETIFY_API_KEY = args['api-key']
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. 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.4.6
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. 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.4.5
2 findingsThis version was published by a different npm account than previous versions on 2026-01-10. 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.4.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-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.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.