registry / @trycodev/cli / 0.8.0
@trycodev/cli@0.8.0
Secure CoDev cloud coding-agent authentication CLI
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected source shows explicit account and setup flows, with credentials sent to the configured CoDev API and no package install hook. Scanner flags for network access, environment access, and child processes 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 runs login, a provider-auth command, setup, or another CLI command that uses the saved account.
Impact
No hidden transfer to an unrelated recipient, install-time execution, or unconsented configuration change was established.
Mechanism
The CLI sends authentication data or its saved bearer token to endpoints on the configured API base, which defaults to the CoDev service.
AI rationale
The inspected source shows explicit account and setup flows, with credentials sent to the configured CoDev API and no package install hook. Scanner flags for network access, environment access, and child processes correspond to these product functions and do not establish malicious behavior.
Network endpoints1
www.trycodev.com
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists only test and typecheck scripts; it has no install lifecycle hook.
- Authentication and agent setup run through explicit CLI commands; setup connects only agents found on the machine and writes the CoDev connector to Codex configuration.
- Provider credentials are read after official provider login and sent to CoDev authentication endpoints using the saved CLI token.
- The API defaults to https://www.trycodev.com; the operator can configure another API URL, which is saved and used for authenticated requests.
- Connector-token and project-sharing requests use the configured CoDev API base; no unrelated recipient or hidden credential transfer was identified.
- Codex setup updates its existing configuration through a merger and restores the prior file if its validation check fails.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
UrlStrings
Source & flagged code
5 flaggedsrc/share-git.mjsView file
1import { spawn } from "node:child_process";
L2:
High
•matchType = previous_version_dangerous_delta
matchedPackage = @trycodev/cli@0.7.0
matchedIdentity = npm:QHRyeWNvZGV2L2NsaQ:0.7.0
similarity = 0.882
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
src/share-git.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 Critical3 High3 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationsrc/client.mjs
HighChild Processsrc/share-git.mjs
HighSame File Env Network Executionsrc/client.mjs
HighPrevious Version Dangerous Deltasrc/share-git.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptosrc/share-files.mjs
LowFilesystem
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @trycodev/cli@0.8.0.
See all versions of @trycodev/cli for other recorded verdicts.
- Review the evidence and your use of @trycodev/cli@0.8.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.