spacecode@2.16.91
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 23h ago · by lpm-firewall-aiThe default API destination and proxy are package-aligned, so the scanner’s fixed unofficial gateway claim is not supported. However, a configurable backend URL receives stored bearer tokens without a host restriction, leaving a conditional credential exposure risk; downgrade to a warning.
Decision evidence
public snapshot- The CLI and MCP entry points create clients whose destination can come from an environment variable or saved configuration.
- The CLI attaches its stored authentication token as a bearer credential to requests sent to that destination.
- The CLI provides an explicit command option for saving a backend URL, but source shows no host restriction before the saved token is sent.
- The MCP entry point uses the configured backend URL and has a matching bearer-token request path.
- The default backend is the package’s SpaceCode service, and the flagged API proxy is also on a SpaceCode domain.
- The alternate backend is selected through configuration; inspected source does not show automatic redirection to a publisher-selected unrelated host.
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.91.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.91 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.