codiedev@0.9.59
Connect Claude Code, Codex, Cursor, OpenCode, or VS Code Copilot to Codiedev for team session capture and artifact collaboration — and run the governed Codie harness
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged execution path uses shell-disabled subprocess calls, and the credential pointers send the Codiedev token to the configured Codiedev backend. The reviewed capture adapter is installed through the connect flow and matches the package’s stated purpose.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs Codiedev commands; capture hooks operate after the user connects an integration and uses a supported coding agent.
Impact
No malicious impact identified. Intended effects include session capture and interaction with Codiedev services.
Mechanism
The CLI uses the configured Codiedev backend for token validation and capture-related checks. The harness uses a Codiedev gateway, and the reviewed reverse-ticket subprocess uses shell-disabled argument arrays.
AI rationale
The flagged execution path uses shell-disabled subprocess calls, and the credential pointers send the Codiedev token to the configured Codiedev backend. The reviewed capture adapter is installed through the connect flow and matches the package’s stated purpose.
Evidence
~/.config/opencode/plugins/codiedev.js
Network endpoints2
config.backendUrl (configured Codiedev backend)gateway.codiedev.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a Codiedev integration for team session capture and a governed coding harness.
- The doctor command sends its token to the configured backend for validation and uses that same configured backend for capture checks.
- The reverse-ticket helper runs subprocesses with argument arrays and explicitly sets shell to false.
- OpenCode capture adapter installation is part of the connect command flow.
Evidence against
- The package reads a Codiedev token and sends it to the configured backend during doctor checks.
- The capture hooks process and upload session data as part of the package’s stated purpose.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/hook.jsView file
43const http = __importStar(require("http"));
L44: const child_process_1 = require("child_process");
L45: const utils_1 = require("./utils");
High
dist/commands/reverseTicket.jsView file
12* caller pastes in. `parsePrOrMrUrl` only bounds those segments to "no slash",
L13: * so they can still carry `$(…)`, backticks or `;` — which a `shell: true`
L14: * invocation would execute. Passing argv directly means the shell never sees
High
dist/codie.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = codiedev@0.9.24
matchedIdentity = npm:Y29kaWVkZXY:0.9.24
similarity = 0.526
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical5 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/codie.js
HighChild Processdist/hook.js
HighShelldist/commands/reverseTicket.js
HighSandbox Evasion Gated Capabilitydist/codie.js
HighCross File Remote Execution Contextdist/utils.js
HighSemantic Analysis Limitedassets/git-refs.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to codiedev@0.9.59.
See all versions of codiedev for other recorded verdicts.
- Review the evidence and your use of codiedev@0.9.59 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.