spacecode@2.16.19
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner’s credential-redirect claim: a supplied key bypasses the proxy, while the default proxy uses a SpaceCode endpoint and a proxy marker. The reviewed agent integration scans around but excludes .claude in one path and reads existing repository command files in another; no malicious behavior was established.
Decision evidence
public snapshot- The manifest exposes the CLI and MCP server as package entrypoints.
- The CLI’s repository scan skips the .claude directory.
- The REPL reads existing repository command files under .claude/commands.
- A caller-supplied API key is set directly; without one, the CLI uses a proxy marker rather than forwarding that key.
- The launch option describes a supplied API key as bypassing the proxy, and passes it to launch setup.
- The configured API and backend endpoints use SpaceCode domains.
- The MCP server connects through standard I/O.
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.16.19.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.19 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.