spacecode@2.16.20
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no lifecycle hooks and did not substantiate the scanner’s credential-redirection claim. The flagged agent-related code reads or scans project files; no attack surface was established.
Decision evidence
public snapshot- The manifest defines CLI and MCP entrypoints and contains no lifecycle script.
- The login command validates supplied SpaceCode API keys and saves them through the local auth-storage helper.
- The configured API endpoints use SpaceCode domains.
- The flagged CLI location scans files and skips the .claude directory; the flagged REPL location reads project-local Claude command files.
- The MCP entrypoint is a command-line server, with no install-time behavior identified.
- The scanner’s credential-redirect claim was not supported by the inspected login path: the supplied API key is saved locally, and the inspected default API endpoints are SpaceCode domains.
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.20.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.20 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.