spacecode@2.17.11
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 6h ago · by lpm-firewall-aiSource inspection did not confirm the scanner’s alleged credential redirection or persistence: the API defaults are SpaceCode endpoints, and the sign-in flow uses the SpaceCode app. The reviewed dependency snapshots show expected library entrypoints; scanner similarity labels alone do not establish malicious behavior.
Decision evidence
public snapshot- The manifest declares the CLI entrypoints and runtime dependencies; it has no install lifecycle hook.
- The CLI uses SpaceCode API defaults, sends its saved token to its configured API base, and obtains login credentials through the SpaceCode sign-in flow.
- The REPL’s API proxy default is the same SpaceCode gateway.
- The inspected MCP SDK, Chalk, and Commander snapshots expose their expected library entrypoints.
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.11.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.17.11 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.