codiedev@0.9.68
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 has no install-time hook, and the new harness is launched by the user and installs its declared OpenCode engine on demand. Connected prompt discovery and capture use the configured Codiedev service as part of the package's stated purpose; no unrelated credential destination or chosen-target account action was found.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the TypeScript build; there is no install hook.
- The codie command requires a Codiedev key or connected configuration before starting the harness.
- The OpenCode engine is installed as the pinned opencode-ai package only when codie needs it.
- The explicit connect flow installs named session-capture and skill-discovery integrations.
- Prompt text is sent to the configured Codiedev backend for the stated team-skill discovery feature, and only when configuration exists.
- Doctor sends the Codiedev token to the configured backend's token-validation endpoint.
- Connected UserPromptSubmit hooks send prompt text to the configured Codiedev backend for skill discovery.
Source & flagged code
6 flaggedFindings
Affected versions and remediation
This report applies to codiedev@0.9.68.
See all versions of codiedev for other recorded verdicts.
- Review the evidence and your use of codiedev@0.9.68 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.