@smithery/sdk
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 |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): SLSA provenance via CI/CD Sigstore attestation; strong supply chain integrity signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA provenance; CI/CD publishing pattern for smithery-ai org. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dependency; phantom-dep heuristic misfires on this package's build structure. | ai | |
| phantom-deps | phantom-dep:json-schema | AI (phantom-deps): json-schema is a declared runtime dependency; phantom-dep heuristic misfires on this package's build structure. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 0 / 4 | |
| 4.2.1 | 0 / 4 | |
| 4.2.0 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.1 | 0 / 4 | |
| 4.0.0 | 0 / 4 | |
| 3.0.1 | 6 / 10 | |
| 3.0.0 | 6 / 10 | |
| 2.0.0 | 10 / 9 | |
| 1.7.5 | 10 / 9 |
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.