spacecode@2.16.74
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 1d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner’s credential-redirection or malware similarity findings. The observed authentication and REPL requests target configured service bases with SpaceCode defaults, and no install hook is declared.
Decision evidence
public snapshot- package.json routes the CLI and MCP commands to their bundles and declares no lifecycle script.
- The CLI attaches its token to requests at the configured API base; its default API and proxy endpoints are SpaceCode services.
- Sign-in requests a device code from the configured or default SpaceCode auth service, displays the approval code and URL, then saves the returned key.
- The REPL uses a configurable backend URL that defaults to SpaceCode for authenticated product API requests.
- The MCP entrypoint uses standard input and output transport; inspected dependency snapshots show MCP, terminal styling, and CLI components.
- PostHog reporting requires a supplied API key; the launch event includes launch option flags.
- Scanner similarity and credential-redirection labels were not confirmed by the inspected source.
Source & flagged code
11 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.74.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.74 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.