spacecode@2.17.13
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe source confirms that an existing Anthropic key can be sent to SpaceCode’s API gateway without a recipient-specific confirmation in the prompt path. Because the gateway is package-aligned and no separate attack behavior was established, this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The REPL checks ANTHROPIC_API_KEY before reading the saved SpaceCode auth token, and uses the resolved key for its prompt client.
- It sends prompts to /v1/messages with the resolved key as x-api-key. The default gateway is api.spacecode.app, and this path shows no recipient-specific confirmation.
- The recipient is SpaceCode’s branded API gateway, which the REPL also uses for model selection; the inspected source does not show the key being sent to an unrelated recipient.
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.13.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.17.13 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.