@varveai/adit-cli@1.0.6
AI Development Intent Tracker — Transparent Time Machine for your codebase
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged process execution and agent configuration are tied to explicit update or cloud-agent commands. The status-line payload contains session metadata and is posted to a loopback hook server; the reviewed source does not show unrelated credential exfiltration or concealed automatic behavior.
Decision evidence
public snapshot- The Claude cloud integration is an explicit `adit cloud claude` command that connects a local Claude CLI to adit-cloud.
- The command requires existing cloud credentials and uses the configured, credential-associated, or default cloud server URL.
- The generated status-line hook posts model, effort, session, transcript-path, and working-directory metadata to a hook server bound to 127.0.0.1.
- Claude hook configuration is written under the project’s `.claude` directory when the cloud command starts; persistent hook repair is limited to projects already recorded as connected to Claude Code.
- Self-update subprocesses are confined to the explicit update command; the package declares build and typecheck scripts but no lifecycle scripts.
Source & flagged code
4 flaggedPackage source references child process execution.
dist/commands/self-update.jsView on unpkg · L8Package source invokes a package manager install command at runtime.
dist/commands/self-update.jsView on unpkg · L124Findings
Affected versions and remediation
This report applies to @varveai/adit-cli@1.0.6.
See all versions of @varveai/adit-cli for other recorded verdicts.
- Review the evidence and your use of @varveai/adit-cli@1.0.6 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.