clavue-v1@1.43.1
Clavue v1: lightweight four-slot (main/light/plan/review) multi-model coding CLI on the execution-first engine — overlapped cross-family review, official Clavue cloud preset (api.clavue.com) alongside any Messages-compatible provider, learned context ceil
AI Security Review
scanned 4d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete credential theft. The flagged evaluation, process execution, and network behavior are consistent with CLI, dependency, proxy, and package-aligned diagnostics functions.
Decision evidence
public snapshot- package.json exposes a command-line entry point and lists build and validation scripts, with no install lifecycle hook.
- The incident reporter redacts common secret patterns, sends reports only when enabled by its settings or environment gate, and posts to the Clavue incident service by default.
- The reporter sends incident records containing diagnostic details and client metadata; this is package-aligned reporting, not evidence of credential theft.
- The flagged dynamic evaluation in Ajv generates a serializer from schema code, and the sandbox proxy checks its filter before allowing a connection.
- The flagged process execution in mao-command.js invokes a command with supplied arguments and options as part of the CLI runtime.
- No inspected source establishes an install-time attack, credential harvesting, or an unconsented transfer to an unrelated recipient.
Source & flagged code
12 flagged · loading sourcePackage source references child process execution.
dist/mao-command.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to clavue-v1@1.43.1.
See all versions of clavue-v1 for other recorded verdicts.
- Review the evidence and your use of clavue-v1@1.43.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.