iclavue@13.0.0
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 install hook is transparent and narrowly scoped to bundled files, with no observed network, credential, self-dependency, or foreign control-surface behavior. Flagged runtime modules provide CLI and provider functionality rather than an install-time attack chain.
Decision evidence
public snapshot- The package has an automatic postinstall hook.
- The postinstall hook only makes bundled pager files executable in its own dist/native directory.
- The flagged command module is a built package artifact, not an install hook.
- The flagged OpenAI adapter is a built package artifact.
- The bundled sandbox CLI runs a command supplied by its explicit command-line user.
- No self-dependency on iclavue was found.
- No install-time network request, credential collection, or project-control-surface write was found.
- The postinstall script limits writes to chmod on matching bundled pager files.
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@13.0.0.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@13.0.0 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.