spacecode@2.16.99
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 22h ago · by lpm-firewall-aiThe inspected source supports ordinary SpaceCode CLI, REPL, and MCP behavior, with no install hook or confirmed credential redirect. The scanner’s similarity and credential-redirection labels do not establish malicious behavior in these source paths.
Decision evidence
public snapshot- The manifest exposes CLI and MCP entrypoints and declares no install lifecycle hook.
- The CLI sends proxy-mode requests to the SpaceCode API and saves a validated SpaceCode API key through its login flow.
- The REPL reads caller-provided API key environment variables; its inspected use is credential configuration for the product.
- The inspected dependency manifests and entrypoints show ordinary SDK, terminal styling, and command-line parsing exports.
- The MCP entrypoint starts a stdio server.
- Telemetry sends only when a PostHog key is supplied through the environment.
- Static similarity and credential-redirect labels are not supported by the inspected source: the proxy host is SpaceCode’s API, and login saves a SpaceCode key.
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.99.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.99 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.