codiedev@0.9.71
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 hook, and the flagged credential flows fit its documented CLI and harness behavior: Codiedev credentials go to the configured Codiedev backend, while the Anthropic key is shown for a Claude Code CI step. The available evidence does not establish hidden or unauthorized behavior.
Decision evidence
public snapshot- The manifest defines command-line binaries and only a prepublishOnly build script; it has no install hook.
- The doctor command sends its configured Codiedev token to the configured backend's token-validation endpoint.
- The pack documentation passes ANTHROPIC_API_KEY to the explicitly invoked Claude Code step in generated CI examples.
- The codie command requires a Codiedev gateway key or connected account token before continuing.
- The codie launcher passes repository metadata to its child runtime when the user invokes the command.
- The package describes session capture and a governed coding harness, consistent with its CLI and network behavior.
- The Anthropic key appears in a CI example as an environment variable for Claude Code, not as a value sent to the Codiedev backend.
Source & flagged code
6 flaggedFindings
Affected versions and remediation
This report applies to codiedev@0.9.71.
See all versions of codiedev for other recorded verdicts.
- Review the evidence and your use of codiedev@0.9.71 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.