@contractspec/app.provider-ranking-mcp
**MCP server that exposes provider-ranking operations and resources for benchmark ingestion, ranking refreshes, and leaderboard queries.**
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:@contractspec/module.provider-ranking | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo packages that may be used indirectly. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.6.31 | 8 / 5 | |
| 1.6.30 | 8 / 5 | |
| 1.6.29 | 8 / 5 | |
| 1.6.28 | 8 / 5 | |
| 1.6.27 | 8 / 5 | |
| 1.6.26 | 8 / 5 | |
| 1.6.25 | 8 / 5 | |
| 1.6.24 | 8 / 5 | |
| 1.6.23 | 8 / 5 | |
| 1.6.22 | 8 / 5 | |
| 1.6.20 | 8 / 5 | |
| 1.6.19 | 8 / 5 | |
| 1.6.18 | 8 / 5 | |
| 1.6.17 | 8 / 5 | |
| 1.6.16 | 8 / 5 | |
| 1.6.15 | 8 / 5 | |
| 1.6.14 | 8 / 5 | |
| 1.6.12 | 8 / 5 | |
| 1.6.10 | 8 / 5 | |
| 1.6.7 | 8 / 5 | |
| 1.6.6 | 8 / 5 | |
| 1.6.5 | 8 / 5 | |
| 1.6.4 | 8 / 5 | |
| 1.6.3 | 8 / 5 | |
| 1.6.1 | 8 / 5 | |
| 1.6.0 | 8 / 5 | |
| 1.5.0 | 8 / 5 | |
| 1.4.5 | 8 / 5 | |
| 1.4.4 | 7 / 5 | |
| 1.4.3 | 7 / 5 | |
| 1.4.2 | 7 / 5 | |
| 1.4.0 | 7 / 5 | |
| 1.3.3 | 7 / 5 | |
| 1.3.2 | 7 / 5 | |
| 1.3.1 | 7 / 5 | |
| 1.3.0 | 7 / 5 | |
| 1.2.0 | 7 / 5 | |
| 1.1.0 | 7 / 5 | |
| 1.0.2 | 7 / 5 |
v1.6.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.