registry / @trycodev/cli / 0.4.0
@trycodev/cli@0.4.0
Secure CoDev cloud coding-agent authentication CLI
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe manifest has no install hook, and source inspection ties provider credential handling to explicit authentication commands that send data to the configured CoDev API. The scanner’s execution and network indicators correspond to these product functions and do not establish malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes a CLI command such as login, codex-auth, claude-auth, cursor-auth, or coordinate.
Impact
The inspected code does not establish covert credential transfer, automatic installation behavior, or another concrete attack.
Mechanism
Authentication data is sent by command handlers to the configured CoDev API; git coordination uses the git executable with an argument list.
AI rationale
The manifest has no install hook, and source inspection ties provider credential handling to explicit authentication commands that send data to the configured CoDev API. The scanner’s execution and network indicators correspond to these product functions and do not establish malicious behavior.
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
- package.json exposes the CLI entry point and lists only test and typecheck scripts; no installation lifecycle hook is configured.
- Provider credential handling occurs in explicit authentication commands: the CLI reads credential files or command output and submits them through authenticated requests.
- The Codex, Claude, and Cursor authentication handlers are dispatched by named CLI commands; the Cursor auth-file candidates are read from a temporary home.
- The git helper invokes git with an argument array and bounded execution options.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
UrlStrings
NoLicense
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 Critical3 High3 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationsrc/client.mjs
HighChild Processsrc/coordinate-git.mjs
HighSame File Env Network Executionsrc/client.mjs
HighPrevious Version Dangerous Deltasrc/client.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @trycodev/cli@0.4.0.
See all versions of @trycodev/cli for other recorded verdicts.
- Review the evidence and your use of @trycodev/cli@0.4.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.