spacecode@2.17.10
⚠ Under reviewSpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 8h ago · by lpm-firewall-aiThe inspected login and proxy paths use SpaceCode endpoints and do not establish credential theft or another concrete attack. Source for declared runtime dependencies remains unresolved, so manual review is appropriate.
Decision evidence
public snapshot- package.json lists listr2, open, and zod as runtime dependencies, but their source was not available in the inspected snapshot, leaving their behavior unresolved.
- The inspected launcher source configures the agent to use the SpaceCode proxy by default and uses a SpaceCode API key when one is supplied; this does not establish an unrelated credential recipient.
- The login flow uses app.spacecode.app, and SpaceCode API tokens are sent to the configured SpaceCode backend.
- The manifest declares no lifecycle scripts; the reviewed credential and proxy behavior is part of the CLI’s sign-in and agent-launch flows.
Source & flagged code
12 flagged · loading sourceManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsFindings
Affected versions and remediation
This report applies to spacecode@2.17.10.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.17.10 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.