spacecode@2.16.8
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected credential and agent-integration paths support ordinary SpaceCode CLI behavior. Scanner similarity labels are not source evidence of an attack; the reviewed source did not establish credential redirection or agent configuration abuse.
Decision evidence
public snapshot- package.json exposes two CLI entrypoints and defines no install lifecycle script.
- The proxy URL resolves to the fixed SpaceCode API endpoint.
- Proxy mode sets a placeholder API key and the SpaceCode proxy URL; a custom API key is used only when supplied as an option.
- The authenticated API client attaches its token to requests sent to its configured service base URL.
- The flagged `.claude` code reads repository command and skill files; it does not mutate agent settings.
- The MCP entrypoint starts a server over standard input and output.
- The scanner’s credential-redirection label is not supported by the inspected source: the proxy defaults to SpaceCode’s API endpoint, and no unrelated credential recipient was found in the inspected paths.
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.8.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.8 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.