codiedev@0.9.24
Connect Claude Code, Codex, Cursor, or VS Code Copilot to Codiedev for org-wide session capture and artifact collaboration
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe risky primitives are package-aligned, token-gated, and activated by an explicit connect flow rather than install/import-time execution. I found no credential harvesting beyond the user-provided API token, no hidden lifecycle execution, and no unconsented AI-agent control-surface mutation.
Decision evidence
public snapshot- package.json has no install/postinstall hook; prepublishOnly is build-only and not run for consumers.
- Entrypoints are explicit CLIs: codiedev and codiedev-hook, with connect prompting for a Codiedev token.
- dist/connect.js validates token against cli.codiedev.com before saving ~/.codiedev/config.json and installing hooks.
- dist/hook.js reads configured token and posts session/transcript events to configured backend as documented session capture behavior.
- dist/backup/run.js auto-backs up selected markdown artifact files only after hook installation and skips AGENTS.md/CLAUDE.md/README.md, .git, node_modules, dist, build.
- dist/backup/match.js contains a BOM-tolerant regex, not a Trojan Source control-flow trick.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/hook.jsView on unpkgFindings
Affected versions and remediation
This report applies to codiedev@0.9.24.
See all versions of codiedev for other recorded verdicts.
- Review the evidence and your use of codiedev@0.9.24 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.