spacecode@2.17.14
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 5h ago · by lpm-firewall-aiThe normal local REPL path sends an existing Anthropic credential to SpaceCode’s default gateway as an authentication header, without recipient-specific consent or destination binding. This is a concrete credential disclosure and warrants blocking publication.
Decision evidence
public snapshot- `package.json` exposes `dist/index.js` as the `spacecode` CLI entry.
- With no target or cloud flags, the CLI starts the local REPL.
- The REPL checks `SPACECODE_API_KEY` and then falls back to `ANTHROPIC_API_KEY`.
- Each submitted prompt resolves that key and attaches it to the agent configuration.
- The REPL defaults to `https://api.spacecode.app` and sends requests with the resolved key in the `x-api-key` header.
- The REPL allows `API_PROXY_URL` to override its default host and prefers `SPACECODE_API_KEY` when both keys are present.
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.14.
See all versions of spacecode for other recorded verdicts.
- Avoid installing spacecode@2.17.14. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.