Back to plugin
Pluginv0.2.14
ClawScan security
Openclaw Murf Plugin · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 22, 2026, 7:30 AM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill is internally consistent with its stated purpose: a Murf AI TTS provider that only needs a Murf API key and uses the Murf endpoints described in the docs.
- Guidance
- This plugin appears to do exactly what it claims: provide Murf Falcon TTS for OpenClaw and it only requires your Murf API key. Before installing: (1) prefer installing from the listed ClawHub or npm package so you get the published build; (2) verify the MURF_API_KEY you supply has only the permissions you expect and rotate it if you later uninstall or suspect compromise; (3) run it in a test workspace first to ensure it behaves as expected; and (4) review the openclaw.plugin.json and the bundled dist/ code if you need extra assurance (the repo contains source and a build pipeline rather than any opaque external installers).
Review Dimensions
- Purpose & Capability
- okName/description, documentation (SKILL.md), openclaw.plugin.json, package.json and source files all align: this is a Murf Falcon TTS OpenClaw provider that requires a Murf API key (MURF_API_KEY). No unrelated credentials or services are requested.
- Instruction Scope
- okRuntime instructions only cover installing/enabling the plugin, setting MURF_API_KEY, configuring provider settings, and running tests (live tests gated behind MURF_API_KEY). The code and SKILL.md reference only Murf API endpoints and OpenClaw config commands; there are no instructions to read unrelated files, exfiltrate data, or call unexpected endpoints.
- Install Mechanism
- noteNo explicit install spec in the skill bundle (instruction-only), but the repo contains packaged source (dist) and build scripts intended to be installed via ClawHub or npm. There are no downloads from untrusted URLs or archive extraction steps in the skill metadata. The presence of a pnpm lockfile with many packages is normal for a Node project but is only relevant if you build/install locally.
- Credentials
- okThe plugin declares and uses a single credential: MURF_API_KEY (primary and provider auth). No other secret env vars, keys, or unrelated credentials are requested or referenced in the code or docs.
- Persistence & Privilege
- okalways is false and the plugin is user-invocable. The skill does not request elevated platform privileges, nor does it modify other plugins' configs beyond standard OpenClaw plugin behavior. Autonomous invocation is allowed by default (disable-model-invocation is false), which is expected for skills.