← Home

@aiwerk/openclaw-mcp-bridge

npm Repository Homepage

OpenClaw MCP plugin — thin wrapper around @aiwerk/mcp-bridge for seamless MCP server integration

35
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

agbergsmann

Keywords

openclawmcpmodel-context-protocolpluginbridgeaiagenttools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@aiwerk/mcp-bridge AI (dependencies): Sibling package from the same AIWerk org; expected internal dependency for this wrapper package. ai
semgrep semgrep:env-spread AI (semgrep): This package is a stdio transport bridge that legitimately merges process.env with user config to pass environment variables to spawned MCP server subprocesses. No exfiltration path exists; this is the correct pattern for this use case. ai
provenance no-provenance AI (provenance): AIWerk org packages consistently lack Sigstore provenance; absence is common (~88% of npm) and not a risk signal for this package. ai
phantom-deps phantom-dep:@sinclair/typebox AI (phantom-deps): @sinclair/typebox is declared as a runtime dep and used in config/type definitions; phantom detection is a false positive for this package's usage pattern. ai

Versions (showing 35 of 35)

Version Deps Published
0.14.1 2 / 4
0.14.0 2 / 4
0.13.6 2 / 4
0.13.5 2 / 4
0.13.4 2 / 4
0.13.3 2 / 4
0.13.2 2 / 4
0.13.1 2 / 4
0.13.0 2 / 4
0.12.2 2 / 4
0.12.1 2 / 4
0.12.0 2 / 4
0.11.7 2 / 4
0.11.6 2 / 4
0.11.5 2 / 4
0.11.4 2 / 3
0.11.3 2 / 3
0.11.2 2 / 3
0.11.1 2 / 3
0.11.0 2 / 3
0.10.9 2 / 3
0.10.8 2 / 3
0.10.7 2 / 3
0.10.6 2 / 3
0.10.5 2 / 3
0.10.4 2 / 3
0.10.3 2 / 3
0.10.2 2 / 3
0.10.1 2 / 3
0.10.0 2 / 3
0.9.4 1 / 3
0.9.3 1 / 3
0.9.2 1 / 3
0.9.1 1 / 3
0.9.0 1 / 3

v0.14.1

1 finding
INFO No provenance attestation provenance

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

v0.14.0

1 finding
INFO No provenance attestation provenance

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

v0.13.6

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.

v0.13.5

1 finding
INFO No provenance attestation provenance

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

v0.13.4

1 finding
INFO No provenance attestation provenance

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

v0.13.3

1 finding
INFO No provenance attestation provenance

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

v0.13.2

1 finding
INFO No provenance attestation provenance

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

v0.13.1

1 finding
INFO No provenance attestation provenance

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

v0.13.0

1 finding
INFO No provenance attestation provenance

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

v0.12.2

1 finding
INFO No provenance attestation provenance

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

v0.12.1

1 finding
INFO No provenance attestation provenance

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

v0.12.0

1 finding
INFO No provenance attestation provenance

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

v0.11.7

1 finding
INFO No provenance attestation provenance

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

v0.11.6

1 finding
INFO No provenance attestation provenance

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

v0.11.5

1 finding
INFO No provenance attestation provenance

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

v0.11.4

1 finding
INFO No provenance attestation provenance

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

v0.11.3

1 finding
INFO No provenance attestation provenance

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

v0.11.2

1 finding
INFO No provenance attestation provenance

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

v0.11.1

1 finding
INFO No provenance attestation provenance

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

v0.11.0

1 finding
INFO No provenance attestation provenance

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

v0.10.9

1 finding
INFO No provenance attestation provenance

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

v0.10.8

1 finding
INFO No provenance attestation provenance

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

v0.10.7

1 finding
INFO No provenance attestation provenance

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

v0.10.6

1 finding
INFO No provenance attestation provenance

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

v0.10.5

1 finding
INFO No provenance attestation provenance

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

v0.10.4

1 finding
INFO No provenance attestation provenance

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

v0.10.3

1 finding
INFO No provenance attestation provenance

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

v0.10.2

1 finding
INFO No provenance attestation provenance

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

v0.10.1

1 finding
INFO No provenance attestation provenance

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

v0.10.0

1 finding
INFO No provenance attestation provenance

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

v0.9.4

2 findings
HIGH env-spread: transport-stdio.ts:32 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/AIWerk/openclaw-mcp-bridge/blob/2bbc2e12921a0219b9a63e6f1d40ff1ad72c9c79/transport-stdio.ts#L32 30 | if (!this.config.command) return; 31 | > 32 | const env = { ...process.env, ...resolveEnvRecord(this.config.env || {}, "env key") }; 33 | const args = resolveArgs(this.config.args || [], env); 34 |

INFO No provenance attestation provenance

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

v0.9.3

2 findings
HIGH env-spread: transport-stdio.ts:32 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/AIWerk/openclaw-mcp-bridge/blob/6c616cb2da79dfc3474d85ed1757b6033e902cae/transport-stdio.ts#L32 30 | if (!this.config.command) return; 31 | > 32 | const env = { ...process.env, ...resolveEnvRecord(this.config.env || {}, "env key") }; 33 | const args = resolveArgs(this.config.args || [], env); 34 |

INFO No provenance attestation provenance

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

v0.9.2

2 findings
HIGH env-spread: transport-stdio.ts:32 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/AIWerk/openclaw-mcp-bridge/blob/07b671e37d40e36368c5ed10a82c57f4d72fa116/transport-stdio.ts#L32 30 | if (!this.config.command) return; 31 | > 32 | const env = { ...process.env, ...resolveEnvRecord(this.config.env || {}, "env key") }; 33 | const args = resolveArgs(this.config.args || [], env); 34 |

INFO No provenance attestation provenance

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

v0.9.1

2 findings
HIGH env-spread: transport-stdio.ts:32 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/AIWerk/openclaw-mcp-bridge/blob/4f036655a5fccf5c7ec924ac1845a900061eba43/transport-stdio.ts#L32 30 | if (!this.config.command) return; 31 | > 32 | const env = { ...process.env, ...resolveEnvRecord(this.config.env || {}, "env key") }; 33 | const args = resolveArgs(this.config.args || [], env); 34 |

INFO No provenance attestation provenance

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

v0.9.0

2 findings
HIGH env-spread: transport-stdio.ts:32 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/AIWerk/openclaw-mcp-bridge/blob/c1e14a96e14a5f8608c71153219fad453998bfb6/transport-stdio.ts#L32 30 | if (!this.config.command) return; 31 | > 32 | const env = { ...process.env, ...resolveEnvRecord(this.config.env || {}, "env key") }; 33 | const args = resolveArgs(this.config.args || [], env); 34 |

INFO No provenance attestation provenance

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