iclavue@11.3.10
Clavue: execution-first AI coding CLI with direct repo tools, provider routing, native workflows, MCP integration, and long-session recovery
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found the postinstall hook limited to optional native pager setup and no concrete attack behavior in the flagged adapter or dependencies. The scanner's dynamic-code and networking matches correspond to bundled AJV serialization and proxy functionality.
Decision evidence
public snapshot- The postinstall hook runs a package script that checks for an optional native pager and changes permissions only on matching pager files.
- The flagged adapter stores a selected provider profile credential in environment variables for provider configuration; inspected source showed no unrelated recipient.
- The flagged dynamic function construction is in AJV's JTD serializer code-generation path.
- The flagged proxy module imports networking primitives for upstream proxy support.
- The manifest's only install lifecycle hook invokes the pager setup script.
- The adapter's inspected credential handling is consistent with provider configuration; no concrete credential exfiltration was established.
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.3.10.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@11.3.10 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.