iclavue@11.2.21
Clavue: execution-first AI coding CLI with direct repo tools, provider routing, native workflows, MCP integration, and long-session recovery
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no concrete attack chain. The scanner indicators resolve to optional native setup and ordinary application or dependency behavior in the excerpts inspected.
Decision evidence
public snapshot- The postinstall hook only checks for an optional platform binary and adjusts its executable permissions; it has no network or project mutation behavior.
- The flagged adapter excerpt shows provider response validation using a supplied profile and request body.
- The MAO command stores state beneath the Clavue configuration directory, partitioned by workspace.
- The parent proxy excerpt documents standard proxy configuration and NO_PROXY matching.
- The AJV finding is ordinary module imports; the inspected excerpt contains no dynamic evaluation.
Source & flagged code
15 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
dist/mao-command.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to iclavue@11.2.21.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@11.2.21 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.