iclavue@11.4.1
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 package has a concrete unsigned remote-native-binary execution path, which is a critical unresolved supply-chain risk. Source inspection did not establish deliberate malicious payload delivery or install-time takeover of a foreign agent control surface.
Decision evidence
public snapshot- The install hook makes every packaged native pager executable.
- The CLI downloads a native executable, saves it, and marks it executable without checking a signature or digest.
- The downloaded pager is selected and spawned as a child process during the interactive UI flow.
- The install hook only changes permissions inside this package's native directory.
- The remote download occurs on a missing pager binary at interactive runtime, not during installation.
- No source evidence showed credential harvesting or transmission to an unrelated endpoint.
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.1.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@11.4.1 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.