@mcpmesh/sdk
TypeScript SDK for MCP Mesh — build distributed AI agents with auto-discovery, dependency injection, and LLM integration
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; consistent CI/CD publishing pattern. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): Pinned to ^4.7.8 which is the patched release; no active CVEs at this range. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version (v2.0.0) with expanded SDK scope; large file count expected. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common; no other risk signals elevate this. | ai | |
| phantom-deps | phantom-dep:mcp-proxy | AI (phantom-deps): SDK pattern; declared as runtime dep used via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google-vertex | AI (phantom-deps): Optional AI provider dep referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Optional AI provider dep referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Optional AI provider dep referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/anthropic | AI (phantom-deps): Optional AI provider dep referenced in config, not directly imported. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 12 / 7 | |
| 2.2.4 | 12 / 7 | |
| 2.2.0 | 12 / 7 | |
| 2.1.0 | 12 / 7 | |
| 2.0.1 | 12 / 7 | |
| 2.0.0 | 12 / 7 | |
| 1.4.1 | 11 / 7 | |
| 1.3.4 | 10 / 7 | |
| 1.3.3 | 10 / 7 | |
| 1.3.1 | 10 / 7 | |
| 1.3.0 | 10 / 7 | |
| 1.2.0 | 10 / 7 | |
| 1.1.0 | 9 / 7 | |
| 1.0.1 | 9 / 7 | |
| 0.9.12 | 9 / 7 | |
| 0.9.10 | 9 / 7 | |
| 0.9.9 | 9 / 7 | |
| 0.9.8 | 9 / 7 | |
| 0.9.7 | 9 / 7 | |
| 0.9.6 | 9 / 7 | |
| 0.9.5 | 9 / 7 | |
| 0.9.4 | 9 / 7 | |
| 0.9.3 | 9 / 7 | |
| 0.9.1 | 9 / 7 | |
| 0.9.0 | 9 / 7 | |
| 0.8.1 | 9 / 7 | |
| 0.8.0 | 9 / 7 |
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.