iclavue@13.7.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 2d ago · by lpm-firewall-aiSource inspection resolved the postinstall and credential-related findings as package-aligned behavior, and the flagged dependency paths contain ordinary library functionality. The scanner labels alone do not establish malicious behavior.
Decision evidence
public snapshot- The npm postinstall hook only changes executable permissions on matching files in the package's own native directory; it does not fetch or run remote code.
- The flagged provider adapter sends compatibility probes to the configured provider profile URL using that profile's credential. The inspected source shows no hidden publisher-selected credential recipient.
- The flagged dependency files contain ordinary OpenTelemetry logging and context APIs, schema validation and conversion code, cache code, and sandbox runtime utilities.
Source & flagged code
20 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
dist/provider-setup.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to iclavue@13.7.0.
See all versions of iclavue for other recorded verdicts.
- Review the evidence and your use of iclavue@13.7.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.