registry / @trycodev/cli / 0.15.0
@trycodev/cli@0.15.0
Secure CoDev cloud coding-agent authentication CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected credential transfers are tied to explicit auth commands and use the configured CoDev API; the update checker only retrieves npm version metadata. Mirroring can run from agent hooks after setup, but the package describes that behavior and gates it on the mirror setting and workspace linkage.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
User-run CLI commands, configured agent hooks, or an update check initiated by those features.
Impact
No malicious behavior identified in the inspected paths. Enabled mirroring uploads agent conversation data to CoDev as the documented feature.
Mechanism
Provider credentials are sent to the configured CoDev API during explicit auth commands. The update check fetches CLI version metadata from npm. The chat mirror is presented as a setup feature and is gated by its enabled setting and workspace linkage.
AI rationale
The inspected credential transfers are tied to explicit auth commands and use the configured CoDev API; the update checker only retrieves npm version metadata. Mirroring can run from agent hooks after setup, but the package describes that behavior and gates it on the mirror setting and workspace linkage.
Evidence
~/.codev/config.json~/.codev/latest.json
Network endpoints2
www.trycodev.comregistry.npmjs.org/@trycodev/cli/latest
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI entry point and has no install, preinstall, or postinstall script.
- Credential forwarding occurs in explicit provider-auth commands and uses the configured CoDev API.
- The update check requests version metadata from the npm registry and saves the result locally.
- The chat mirror is described during setup; its hook requires a recognized agent, a transcript path, and the mirror-enabled setting.
Evidence against
- The mirror can default to enabled when setup runs non-interactively, and its enabled hook starts transcript uploading for linked workspaces.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
16 flaggedsrc/update-check.mjsView file
1import { spawn } from "node:child_process";
L2: import { mkdir, readFile, rename, writeFile } from "node:fs/promises";
High
Child Process
Package source references child process execution.
src/update-check.mjsView on unpkg · L1•matchType = normalized_sha256
matchedPackage = @trycodev/cli@0.14.0
matchedPath = src/update-check.mjs
matchedIdentity = npm:QHRyeWNvZGV2L2NsaQ:0.14.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
src/update-check.mjsView on unpkgsrc/share-files.mjsView file
1import { execFile } from "node:child_process";
L2: import { createHash } from "node:crypto";
...
L46: { maxBuffer: 64 << 20, encoding: "buffer" },
L47: (error, stdout) => resolve(error ? null : stdout),
L48: );
...
L57: if (!out) return null;
L58: return [...new Set(out.toString("utf8").split("\0").filter(Boolean))];
L59: }
Findings
1 Critical14 High3 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationsrc/client.mjs
HighChild Processsrc/update-check.mjs
HighSame File Env Network Executionsrc/client.mjs
HighKnown Malware Source Similaritysrc/client.mjs
HighKnown Malware Source Similaritysrc/update-check.mjs
HighKnown Malware Source Similaritysrc/coordinate-git.mjs
HighKnown Malware Source Similaritysrc/mirror-daemon.mjs
HighKnown Malware Source Similaritysrc/mirror-upload.mjs
HighKnown Malware Source Similaritysrc/mirror.mjs
HighKnown Malware Source Similaritysrc/update.mjs
HighKnown Malware Source Similaritysrc/clone.mjs
Affected versions and remediation
This report applies to @trycodev/cli@0.15.0.
See all versions of @trycodev/cli for other recorded verdicts.
- Review the evidence and your use of @trycodev/cli@0.15.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.