spacecode@2.17.4
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 8h ago · by lpm-firewall-aiSource inspection resolves the scanner’s gateway and persistence signals as normal SpaceCode CLI behavior: the default proxy is SpaceCode-owned, and saved keys are written during login. The manifest and inspected dependency sources show no install-time hook or concrete attack behavior.
Decision evidence
public snapshot- The manifest exposes CLI commands and has no install lifecycle hook.
- The CLI’s default model proxy is a SpaceCode endpoint; without a custom key, it supplies the literal placeholder “proxy.”
- The login command validates a SpaceCode API key and saves it as authentication data.
- The REPL reads keys from the environment or saved authentication and uses them with its model gateway, which defaults to SpaceCode’s proxy.
- The inspected dependency manifests show no preinstall, install, or postinstall hooks; the included dependency source is CLI parsing and terminal styling code.
- The REPL allows an API proxy URL override and sends its resolved key to that gateway; the default destination is SpaceCode’s proxy.
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.4.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.17.4 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.