@jaypie/mcp
Jaypie MCP
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are all from the same @jaypie/* monorepo or well-known packages (semver). Consistent with documented MCP/LLM feature expansion; SLSA provenance confirms CI/CD integrity. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @jaypie/mcp is a scoped package in the established @jaypie namespace; Levenshtein comparison to 'yup' is a false positive — no brand impersonation. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a legitimate declared dependency; phantom detection likely reflects CLI/indirect usage patterns, not a real issue. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a legitimate declared dependency used for CLI tooling; phantom detection is a false positive for this package type. | ai |
Versions (showing 42 of 148)
| Version | Deps | Published |
|---|---|---|
| 0.7.7 | 8 / 8 | |
| 0.7.6 | 8 / 8 | |
| 0.7.4 | 8 / 8 | |
| 0.7.3 | 8 / 8 | |
| 0.7.2 | 8 / 8 | |
| 0.7.1 | 8 / 8 | |
| 0.7.0 | 8 / 8 | |
| 0.6.6 | 7 / 8 | |
| 0.6.5 | 7 / 8 | |
| 0.6.4 | 7 / 8 | |
| 0.6.3 | 7 / 8 | |
| 0.6.2 | 7 / 8 | |
| 0.6.1 | 7 / 8 | |
| 0.6.0 | 7 / 8 | |
| 0.5.0 | 7 / 8 | |
| 0.4.1 | 7 / 7 | |
| 0.4.0 | 7 / 7 | |
| 0.3.4 | 7 / 7 | |
| 0.3.2 | 6 / 7 | |
| 0.3.1 | 5 / 6 | |
| 0.3.0 | 5 / 6 | |
| 0.2.12 | 5 / 6 | |
| 0.2.10 | 5 / 6 | |
| 0.2.9 | 5 / 6 | |
| 0.2.7 | 5 / 6 | |
| 0.2.6 | 5 / 6 | |
| 0.2.5 | 5 / 6 | |
| 0.2.4 | 5 / 6 | |
| 0.2.3 | 5 / 6 | |
| 0.2.2 | 4 / 6 | |
| 0.2.1 | 4 / 6 | |
| 0.1.10 | 4 / 2 | |
| 0.1.9 | 4 / 2 | |
| 0.1.8 | 4 / 2 | |
| 0.1.7 | 4 / 2 | |
| 0.1.6 | 4 / 2 | |
| 0.1.5 | 4 / 2 | |
| 0.1.4 | 4 / 2 | |
| 0.1.3 | 4 / 3 | |
| 0.1.2 | 4 / 1 | |
| 0.1.1 | 4 / 0 | |
| 0.1.0 | 4 / 0 |
v0.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
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.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.5
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.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.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
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.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.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.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.