← Home

@modelcontextprotocol/inspector-cli

30
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jspahrsummerspcarletonfweinbergerthedspashwin-antochafik-antcliffhall

Versions (showing 30 of 30)

Version Deps Published
1.0.0 4 / 3
0.22.0 4 / 3
0.21.2 4 / 3
0.21.1 4 / 3
0.21.0 4 / 3
0.20.0 4 / 3
0.19.0 4 / 3
0.18.0 3 / 0
0.17.5 3 / 0
0.17.2 3 / 0
0.17.1 3 / 0
0.17.0 3 / 0
0.16.8 3 / 0
0.16.7 3 / 0
0.16.6 3 / 0
0.16.5 3 / 0
0.16.4 3 / 0
0.16.3 3 / 0
0.16.2 3 / 0
0.16.1 3 / 0
0.16.0 3 / 0
0.15.0 3 / 0
0.14.3 3 / 0
0.14.2 3 / 0
0.14.1 3 / 0
0.14.0 3 / 0
0.13.0 3 / 0
0.12.0 3 / 0
0.11.0 3 / 0
0.10.2 3 / 0

v1.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.