@contractspec/lib.contracts-runtime-server-mcp
MCP server runtime adapters for ContractSpec contracts
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:zod | AI (phantom-deps): zod is declared as a peer/runtime dep and referenced in config; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.presentation-runtime-core | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for this monorepo package. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 3.8.9 | 5 / 3 | |
| 3.8.8 | 5 / 3 | |
| 3.8.7 | 5 / 3 | |
| 3.8.6 | 5 / 3 | |
| 3.8.5 | 5 / 3 | |
| 3.8.4 | 5 / 3 | |
| 3.8.3 | 5 / 3 | |
| 3.8.2 | 5 / 3 | |
| 3.8.1 | 5 / 3 | |
| 3.8.0 | 5 / 3 | |
| 3.7.20 | 5 / 3 | |
| 3.7.19 | 5 / 3 | |
| 3.7.18 | 5 / 3 | |
| 3.7.17 | 5 / 3 | |
| 3.7.16 | 5 / 3 | |
| 3.7.15 | 5 / 3 | |
| 3.7.14 | 5 / 3 | |
| 3.7.12 | 5 / 3 | |
| 3.7.10 | 4 / 3 | |
| 3.7.7 | 4 / 3 | |
| 3.7.6 | 4 / 3 | |
| 3.7.5 | 4 / 3 | |
| 3.7.4 | 4 / 3 | |
| 3.7.1 | 4 / 3 | |
| 3.7.0 | 4 / 3 | |
| 3.6.0 | 4 / 3 | |
| 3.5.5 | 4 / 3 | |
| 3.5.4 | 4 / 3 | |
| 3.5.3 | 4 / 3 | |
| 3.5.2 | 4 / 3 | |
| 3.5.0 | 4 / 3 | |
| 3.4.3 | 4 / 3 | |
| 3.4.2 | 4 / 3 | |
| 3.4.1 | 4 / 3 | |
| 3.4.0 | 4 / 3 | |
| 3.3.0 | 4 / 3 | |
| 3.2.0 | 4 / 3 | |
| 3.1.1 | 4 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.9.1 | 4 / 3 | |
| 2.9.0 | 4 / 3 | |
| 2.8.0 | 4 / 3 | |
| 2.7.0 | 4 / 3 | |
| 2.6.0 | 4 / 3 | |
| 2.5.0 | 4 / 3 | |
| 2.4.0 | 4 / 3 | |
| 2.3.0 | 4 / 3 | |
| 2.2.0 | 4 / 3 | |
| 2.1.1 | 4 / 3 | |
| 2.1.0 | 4 / 3 | |
| 2.0.0 | 4 / 3 |
v3.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.