iclavue@13.5.0
⚠ Under reviewClavue: execution-first AI coding CLI with direct repo tools, provider routing, native workflows, MCP integration, and long-session recovery
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe inspected lifecycle hook is narrow, and the provider configuration does not establish an unrelated credential recipient. However, the package ships platform-specific native pager executables that the available offline analyses could not resolve, so their runtime behavior remains materially uncertain.
Decision evidence
public snapshot- The package’s CLI commands enter the bundled JavaScript CLI through dist/clavue.js.
- The postinstall hook handles an optional native UI and limits its file changes to pager executables in the package’s native directory.
- Offline analyses identify four bundled native pager executables but cannot resolve their format or behavior.
- The inspected lifecycle code only changes executable permissions on package-owned pager files; it does not establish harmful install-time behavior.
- The inspected provider configuration pairs credentials with a configured API endpoint, defaulting to api.clavue.com.
Source & flagged code
14 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.5.0.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@13.5.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.