Dangerous exec
- Finding
- Shell command execution detected (child_process).
Security checks across static analysis, malware telemetry, and agentic risk
OnDeckLLM is a coherent local dashboard skill, but users should know it installs an external npm package and can read or change local LLM provider configuration.
Install this only if you trust the OnDeckLLM npm package. Before using it, understand that the dashboard can read and update your OpenClaw provider configuration and stores local settings and usage logs under ~/.ondeckllm/. Review any routing or provider changes before syncing them.
VirusTotal findings are pending for this skill version.
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the dashboard gives code from the npm package the ability to run locally on the user’s machine.
The skill depends on a globally installed npm package whose implementation is not included in the provided artifacts. This is disclosed and purpose-aligned, but users must trust that external package.
Requires: Node.js 22+, OnDeckLLM installed (`npm install -g ondeckllm`).
Install only from the expected npm package, verify the publisher/source if possible, and keep it updated.
Running the helper script reads the local process list to report dashboard status.
The included helper script executes a fixed local shell command to check whether the dashboard process is running. It does not take user-controlled command arguments.
const out = execSync("ps aux | grep '[o]ndeckllm' | grep -v 'status.js'", {Use the helper only for local status checks; no additional action is needed based on the provided code.
Dashboard changes can alter which LLM providers and models OpenClaw uses.
The dashboard is explicitly allowed to read and modify OpenClaw provider/routing configuration, which may affect accounts, API usage, and future model selection.
OnDeckLLM reads provider config from `~/.openclaw/openclaw.json` automatically. Changes made in the dashboard sync back to OpenClaw config.
Review provider and routing changes before syncing them back to OpenClaw, especially if the config contains paid API providers.
Local files may retain provider settings, usage history, and preferred model routing after the dashboard is closed.
The skill discloses persistent local storage for provider settings, usage/cost logs, and routing profiles that can influence future use.
OnDeckLLM stores its data in `~/.ondeckllm/`: `config.json` — provider settings, port, Ollama URL; `usage.jsonl` — cost tracking log; `profiles/` — saved batting-order profiles
Review or remove ~/.ondeckllm/ data if you no longer want those settings or logs retained.