@modelcontextprotocol/inspector-server
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 9 / 6 | |
| 0.22.0 | 9 / 6 | |
| 0.21.2 | 9 / 6 | |
| 0.19.0 | 7 / 6 | |
| 0.18.0 | 7 / 6 | |
| 0.17.5 | 7 / 6 | |
| 0.17.2 | 7 / 6 | |
| 0.17.1 | 7 / 6 | |
| 0.17.0 | 7 / 6 | |
| 0.16.8 | 7 / 6 | |
| 0.16.7 | 5 / 5 | |
| 0.16.6 | 5 / 5 | |
| 0.16.5 | 5 / 5 | |
| 0.16.4 | 5 / 5 | |
| 0.16.3 | 5 / 5 | |
| 0.16.2 | 5 / 5 | |
| 0.16.1 | 5 / 5 | |
| 0.16.0 | 5 / 5 | |
| 0.15.0 | 5 / 5 | |
| 0.14.3 | 5 / 5 | |
| 0.14.2 | 5 / 5 | |
| 0.14.1 | 5 / 5 | |
| 0.14.0 | 5 / 5 | |
| 0.13.0 | 5 / 5 | |
| 0.12.0 | 5 / 5 | |
| 0.11.0 | 5 / 5 | |
| 0.10.2 | 5 / 5 | |
| 0.10.1 | 5 / 5 | |
| 0.10.0 | 5 / 5 | |
| 0.9.0 | 5 / 5 | |
| 0.8.2 | 5 / 5 | |
| 0.8.1 | 5 / 5 | |
| 0.8.0 | 5 / 5 | |
| 0.7.0 | 5 / 5 | |
| 0.6.0 | 5 / 5 | |
| 0.5.1 | 5 / 5 | |
| 0.4.1 | 5 / 5 | |
| 0.4.0 | 5 / 5 | |
| 0.3.0 | 6 / 6 | |
| 0.2.7 | 6 / 6 | |
| 0.2.6 | 6 / 6 | |
| 0.2.4 | 6 / 6 | |
| 0.2.3 | 6 / 6 | |
| 0.2.2 | 6 / 6 | |
| 0.2.1 | 6 / 6 | |
| 0.2.0 | 6 / 6 | |
| 0.1.7 | 6 / 6 | |
| 0.1.6 | 6 / 6 | |
| 0.1.5 | 6 / 6 | |
| 0.1.0 | 6 / 6 |
v1.0.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jspahrsummers) than the most recent previously approved version (ashwin-ant) on 2024-11-21, but jspahrsummers is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
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. Only ~12% of npm packages have provenance, so this is common but not ideal.