spacecode@2.16.15
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the inspected credential path handles a caller-supplied SpaceCode key for SpaceCode authentication. The flagged agent-related locations perform project scanning and trust checks; no concrete attack surface was established.
Decision evidence
public snapshot- package.json defines CLI binaries and dependencies but no lifecycle scripts.
- Login validates and saves a caller-supplied SpaceCode API key.
- Agent proxy configuration uses the SpaceCode API endpoint; a custom key is passed only when supplied in options.
- The flagged dist/index.js location skips .claude directories during source scanning.
- The flagged dist/repl.mjs location reads project command files as repo sources and checks their trust status.
- The MCP entrypoint uses stdio; telemetry sends only when POSTHOG_API_KEY is set.
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.15.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.15 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.