clavue-v1@1.31.0
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-aiThe credential transfer is conditional on an explicit router command, and the default destination is package-aligned. Because a configurable origin can receive the saved credential without a destination allowlist, this remains a concrete credential-exposure risk.
Decision evidence
public snapshot- The router command reads a saved credential from the official Clavue provider profile.
- The router origin can be replaced through CLAVUE_ROUTER_ORIGIN, and the token resolver can use the supplied official credential.
- The pull request sends that token as a bearer credential to the selected origin without a host allowlist.
- This transfer is reached through the explicit router pull or load command; the default origin is router.clavue.com.
- The default router destination is the package's Clavue service, and the credential transfer requires an explicit command.
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.31.0.
See all versions of clavue-v1 for other recorded verdicts.
- Review the evidence and your use of clavue-v1@1.31.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.