registry / @trycodev/cli / 0.5.0
@trycodev/cli@0.5.0
Secure CoDev cloud coding-agent authentication CLI
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection found no install hook or covert credential recipient. Provider credential collection is tied to explicit CLI commands, and the client sends it through the configured CoDev API.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes login or an explicit provider authentication command; coordination runs when configured and invoked.
Impact
The inspected transfers support account connection and coordination features; no unrelated recipient or unconsented attack behavior was established.
Mechanism
The client attaches the saved CoDev account token to requests at the configured API URL and posts provider credentials to the corresponding CoDev authentication route.
AI rationale
Source inspection found no install hook or covert credential recipient. Provider credential collection is tied to explicit CLI commands, and the client sends it through the configured CoDev API.
Evidence
package.jsonsrc/client.mjsbin/codev.mjssrc/coordinate-git.mjs
Network endpoints1
www.trycodev.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes bin/codev.mjs and lists only test and typecheck scripts; no install lifecycle hook is declared.
- The client defaults to https://www.trycodev.com, with CODEV_API_URL available as an override; authenticated requests use the saved CoDev token and configured API URL.
- Codex, Claude, and Cursor credentials are collected and posted to their corresponding CoDev CLI authentication routes.
- The CLI dispatches provider credential collection only for explicit codex-auth, claude-auth, and cursor-auth commands; it also reports command errors.
- Configuration is stored under the user's .codev directory by default, and coordination code gathers repository identifiers and changed file and symbol metadata.
- Cursor authentication uses an isolated temporary home and file credential store before sending the resulting auth data to the CoDev route.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flaggedsrc/coordinate-git.mjsView file
1import { execFile } from "node:child_process";
L2: import { createHash } from "node:crypto";
High
Child Process
Package source references child process execution.
src/coordinate-git.mjsView on unpkg · L1src/client.mjsView file
10Source sends the broad process environment to a literal external destination.
L10: import { dirname, join } from "node:path";
L11: import { spawn } from "node:child_process";
L12:
L13: const DEFAULT_API_URL = "https://www.trycodev.com";
L14:
L15: export function configPath(environment = process.env) {
L16: return join(
L17: environment.CODEV_CONFIG_DIR || join(homedir(), ".codev"),
L18: "config.json",
...
L27: const response = await fetch(`${baseUrl}${path}`, options);
L28: const payload = await response.json().catch(() => ({}));
L29: if (!response.ok && response.status !== 202) {
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
src/client.mjsView on unpkg · L10Findings
1 Critical2 High3 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationsrc/client.mjs
HighChild Processsrc/coordinate-git.mjs
HighSame File Env Network Executionsrc/client.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
LowAi Review Evidencesrc/client.mjs
LowAi Review Evidencebin/codev.mjs
Affected versions and remediation
This report applies to @trycodev/cli@0.5.0.
See all versions of @trycodev/cli for other recorded verdicts.
- Review the evidence and your use of @trycodev/cli@0.5.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.