registry / @trycodev/cli / 0.5.1
@trycodev/cli@0.5.1
Secure CoDev cloud coding-agent authentication CLI
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install hook, and the reviewed credential transfers occur through explicit account or provider-auth flows directed to the configured CoDev API. The inspected source does not establish hidden credential collection or an unrelated recipient.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes login, a provider-auth command, setup, or coordination.
Impact
These operations connect the user's account and providers to CoDev; the inspected source does not establish covert collection or an unrelated recipient.
Mechanism
The CLI sends its saved CoDev token to the configured API and sends provider credentials to CoDev authentication routes during provider-auth commands.
AI rationale
The manifest has no install hook, and the reviewed credential transfers occur through explicit account or provider-auth flows directed to the configured CoDev API. The inspected source does not establish hidden credential collection or an unrelated recipient.
Evidence
package.jsonsrc/client.mjsbin/codev.mjssrc/coordinate-git.mjssrc/setup.mjs
Network endpoints1
www.trycodev.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI entry point and contains no install lifecycle hook.
- Saved CoDev credentials are attached to requests sent to the configured CoDev API; its default is the CoDev service.
- Provider-auth commands explicitly invoke Codex, Claude, or Cursor login, then send the resulting credentials to their corresponding CoDev authentication routes.
- Setup is invoked as a CLI command and connects the user's CoDev account and coding agents.
- Coordination gathers Git checkout information for its coordination feature; the inspected excerpt does not show credential collection or an unrelated recipient.
Evidence against
- Provider-auth requests carry provider credentials, and the CoDev API URL can be overridden through environment configuration; the inspected callers are explicit auth commands and the override is caller-selected.
- The package uses network and child-process capabilities for its CLI features, but these facts alone do not establish an attack.
Behavioral surface
ChildProcessCryptoEnvironmentVars
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/setup.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.5.1.
See all versions of @trycodev/cli for other recorded verdicts.
- Review the evidence and your use of @trycodev/cli@0.5.1 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.