codiedev@0.9.60
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 package’s observed network and process behavior aligns with its stated team session capture and governed harness features. It has no install-time hook, and the reviewed credential flow uses a connected Codiedev token with Codiedev endpoints.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User-run Codiedev commands and agent hook events configured for Codiedev.
Impact
Expected package behavior; no unrelated credential destination or unauthorized account action was found.
Mechanism
Hooks send discovery or capture requests to the configured Codiedev backend; the harness uses a connected Codiedev token with the Codiedev gateway.
AI rationale
The package’s observed network and process behavior aligns with its stated team session capture and governed harness features. It has no install-time hook, and the reviewed credential flow uses a connected Codiedev token with Codiedev endpoints.
Evidence
~/.claude/settings.json~/.codiedev/config.json
Network endpoints2
gateway.codiedev.comconfig.backendUrl
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes its purpose as connecting coding agents for team session capture and artifact collaboration.
- The manifest has a prepublishOnly build script, but no preinstall, install, or postinstall script.
- Hook input passes through a capture exclusion check before network requests, transcript reads, or detached work.
- Prompt discovery sends the prompt with the configured Codiedev token to the configured backend URL for skill matching.
- The Codie harness requires an account token supplied by codiedev connect or its documented environment variables, and defaults to the Codiedev gateway.
- The reverse-ticket helper invokes commands with shell disabled.
Evidence against
- When configured, prompt discovery sends free-form prompts to the Codiedev backend on hook events.
- The harness uses the connected Codiedev token for authenticated gateway requests.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
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.60.
See all versions of codiedev for other recorded verdicts.
- Review the evidence and your use of codiedev@0.9.60 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.