iclavue@12.0.10
Clavue: execution-first AI coding CLI with direct repo tools, provider routing, native workflows, MCP integration, and long-session recovery
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete credential theft, remote payload execution, destructive action, or lifecycle self-dependency was found. The remaining risk is user-invoked mutation of existing external AI-provider configuration files.
Decision evidence
public snapshot- The package installs a postinstall hook that changes permissions on bundled native executables.
- The provider feature edits existing external AI-provider configuration files when it changes the active profile.
- It forwards configured provider credentials in API validation requests, but the request destination is the selected profile URL.
- The install hook only scans dist/native and applies executable permissions; it does not launch a binary or use the network.
- No runtime dependency refers back to iclavue, so there is no nested lifecycle self-dependency chain.
- External configuration writes are tied to active-provider updates and only occur for recognized existing configuration sections.
Source & flagged code
13 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@12.0.10.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@12.0.10 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.