spacecode@2.16.18
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found package-aligned cloud endpoints, an explicitly supplied provider-key path that bypasses the proxy, and trust-gated project agent-source handling. The scanner similarity and credential-redirect labels were not substantiated by the inspected behavior.
Decision evidence
public snapshot- package.json exposes CLI binaries and declares no install lifecycle hook.
- The configured API, sandbox, and model proxy endpoints use SpaceCode domains.
- A supplied Anthropic key is used directly; the SpaceCode proxy is configured only when no custom key is supplied.
- The GitHub TODO scanner skips `.claude`; REPL repo sources are treated as unavailable unless their trust status is trusted or session-approved.
- The REPL reads project `.claude/commands` files as repo sources, subject to the repo-source trust check.
- The MCP entrypoint starts a stdio server when invoked.
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.18.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.18 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.