iclavue@12.0.14
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-aiThe postinstall hook is limited to chmod on package-native files, so the evidence does not establish malicious install-hook abuse. The explicit runtime capabilities to rewrite compatible external configuration and fetch a native executable remain unresolved security risk.
Decision evidence
public snapshot- Provider setup explicitly targets existing ccjk and zcf configuration files outside the package.
- Saving a provider profile updates compatible external configuration after persisting Clavue state.
- The bundled CLI can download a native pager executable from the Clavue site during interactive use; no integrity verification is visible in that loader.
- The install hook only makes bundled pager files executable and does not modify user configuration.
- There is no runtime dependency on iclavue or other self-installing lifecycle chain.
- Provider configuration changes are reached through profile save or activation functions, not the install hook.
- The inspected adapter routes configured API requests and does not show credential exfiltration to an unrelated endpoint.
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.14.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@12.0.14 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.