spacecode@2.16.10
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 flow uses SpaceCode’s configured backend and auth service. The scanner’s agent-configuration locations show repository scanning and trust-aware source reading, not an unconsented configuration mutation or credential export.
Decision evidence
public snapshot- package.json has CLI entrypoints and dependencies but no lifecycle scripts.
- The flagged dist/index.js location scans source files; it does not show an agent configuration write.
- The flagged dist/repl.mjs location reads project Claude command files; its repo-source handling checks trust status before loading sources.
- The API client sends its token as a bearer credential to its configured backend URL; the default backend is backend.spacecode.app.
- Login accepts a supplied SpaceCode API key or uses device login at the SpaceCode auth service.
- The MCP entrypoint connects a server over stdio.
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.10.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.10 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.