registry / @varveai/adit-cli / 1.0.10
@varveai/adit-cli@1.0.10
AI Development Intent Tracker — Transparent Time Machine for your codebase
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged hook setup routes events to a loopback relay during cloud-agent use. The process execution and version checks inspected serve the stated CLI update and integration features; no concrete malicious behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Explicit CLI commands, including self-update or cloud-agent use; version checks run for selected commands.
Impact
No unauthorized credential collection, external exfiltration, or install-time action was identified.
Mechanism
The cloud-agent hooks forward payloads to a loopback relay. Version checks contact the package registry or policy endpoint with version information.
AI rationale
The package has no install lifecycle hook, and the flagged hook setup routes events to a loopback relay during cloud-agent use. The process execution and version checks inspected serve the stated CLI update and integration features; no concrete malicious behavior was found.
Evidence
.claude/settings.local.json.claude/adit-cloud-<terminalId>.settings.local.json.codex/hooks.json~/.adit/version-check.json
Network endpoints3
127.0.0.1registry.npmjs.orgadit-cloud.varve.ai
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines only build and typecheck scripts; it has no install lifecycle hook.
- The CLI hook relay binds to 127.0.0.1 and constructs a loopback endpoint.
- The Claude cloud flow installs hooks pointing to that local relay while starting its provider.
- The version-policy check sends the CLI version as a query parameter to the policy endpoint.
Evidence against
- The package uses child-process execution for the explicit self-update command and process inspection in the Codex watcher.
- Claude status-line integration can run the pre-existing user-configured status-line command and sends session metadata to the local relay.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggeddist/commands/self-update.jsView file
8*/
L9: import { execSync } from "node:child_process";
L10: import { existsSync, readFileSync } from "node:fs";
High
Child Process
Package source references child process execution.
dist/commands/self-update.jsView on unpkg · L8196console.log("Installing dependencies ...");
L197: execSync("pnpm install --frozen-lockfile", {
L198: ...showExecOpts,
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/commands/self-update.jsView on unpkg · L196dist/commands/cli-agent/codex/codex-resume-log-watcher.jsView file
184if (process.platform === "win32") {
L185: const { stdout } = await run("powershell.exe", [
L186: "-NoProfile", "-NonInteractive", "-Command",
Findings
1 Critical4 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/cli-agent/claude/hooks-bootstrap.js
HighChild Processdist/commands/self-update.js
HighShelldist/commands/cli-agent/codex/codex-resume-log-watcher.js
HighRuntime Package Installdist/commands/self-update.js
HighSemantic Analysis Limitedpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @varveai/adit-cli@1.0.10.
See all versions of @varveai/adit-cli for other recorded verdicts.
- Review the evidence and your use of @varveai/adit-cli@1.0.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.