@nuxtjs/mcp-toolkit
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Nuxt module pattern; config-referenced deps not directly imported are expected. | ai | |
| phantom-deps | phantom-dep:automd | AI (phantom-deps): Nuxt module pattern; config-referenced deps not directly imported are expected. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): Nuxt module pattern; config-referenced deps not directly imported are expected. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Namespace reservation by established Nuxt core maintainer; 0.0.0 is intentional stub. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Placeholder package by trusted @nuxtjs publisher; sparse metadata is expected for a stub. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentional stub package; no description expected. | ai | |
| provenance | slsa-provenance | AI (provenance): Published via CI/CD with Sigstore SLSA attestation; strong supply chain integrity signal for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.17.2 | 5 / 17 | |
| 0.17.1 | 5 / 17 | |
| 0.16.1 | 5 / 17 | |
| 0.16.0 | 5 / 17 | |
| 0.15.0 | 5 / 17 | |
| 0.14.0 | 3 / 12 | |
| 0.13.4 | 3 / 11 | |
| 0.13.3 | 3 / 11 | |
| 0.13.2 | 3 / 11 | |
| 0.13.1 | 3 / 11 | |
| 0.13.0 | 3 / 11 | |
| 0.12.0 | 3 / 11 | |
| 0.11.0 | 3 / 12 | |
| 0.10.0 | 3 / 12 | |
| 0.8.0 | 8 / 12 | |
| 0.7.0 | 8 / 12 | |
| 0.6.4 | 8 / 12 | |
| 0.6.3 | 8 / 12 | |
| 0.6.2 | 11 / 12 | |
| 0.6.1 | 11 / 12 | |
| 0.6.0 | 11 / 12 | |
| 0.5.2 | 11 / 12 | |
| 0.5.1 | 11 / 12 | |
| 0.5.0 | 11 / 12 | |
| 0.4.1 | 10 / 12 | |
| 0.4.0 | 10 / 12 | |
| 0.3.0 | 10 / 12 | |
| 0.2.0 | 9 / 12 | |
| 0.1.1 | 9 / 12 | |
| 0.1.0 | 9 / 12 | |
| 0.0.1 | 9 / 12 | |
| 0.0.0 | 0 / 0 |
v0.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
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.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.