iclavue@11.4.4
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-aiStatic inspection shows a package-local postinstall permission adjustment, not a malicious lifecycle chain. Scanner labels concerning networking and credentials correspond to a user-invoked AI CLI and do not establish unconsented exfiltration or install-time abuse.
Decision evidence
public snapshot- An automatic postinstall hook runs after installation.
- The hook changes execute permissions on packaged native pager files.
- The hook only resolves paths beneath this package's dist/native directory and makes no network request.
- No runtime dependency on iclavue itself is declared.
- The normal CLI entrypoint loads only when the user invokes a package-provided command.
- No unconsented install-time write to an AI-agent configuration surface was found.
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.4.4.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@11.4.4 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.