codiedev@0.9.56
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 manifest has no install-time hook, and the examined credential and session-data flows go to the configured Codiedev backend or its default gateway for the package’s stated functionality. Process execution supports the launched harness and capture workflow; no unrelated or concealed behavior was found.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the TypeScript build; no install hook is declared.
- The doctor command sends the saved Codiedev token to the configured Codiedev backend for token validation and capture status.
- The Codie launcher requires a Codiedev gateway key or a token saved by connecting a Codiedev account before starting its runtime.
- The session-start hook sends a session ID and timestamp to the configured backend when capture configuration exists.
- The package presents itself as a Codiedev CLI and governed AI coding harness, consistent with the inspected network and process behavior.
- The doctor requests are directed to config.backendUrl, and the harness uses the Codiedev gateway URL by default.
- The flagged process launches support the harness runtime and detached session-capture work; no unrelated payload execution was identified.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/codie.jsView on unpkgFindings
Affected versions and remediation
This report applies to codiedev@0.9.56.
See all versions of codiedev for other recorded verdicts.
- Review the evidence and your use of codiedev@0.9.56 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.