spacecode@2.16.11
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no npm lifecycle hook or concrete attack behavior. The flagged agent and credential-related code supports user-invoked SpaceCode cloud functionality and does not establish unauthorized settings mutation or credential disclosure.
Decision evidence
public snapshot- The manifest exposes CLI and MCP binaries, lists regular dependencies, and defines no npm lifecycle script.
- The runtime defaults its API and proxy to SpaceCode service domains; device sign-in uses a SpaceCode authentication endpoint.
- A supplied custom API key is placed in the cloud agent environment; without one, the runtime configures the SpaceCode proxy.
- The inspected agent-related code skips `.claude` during a local scan and reads repository command files; it does not write agent settings.
- The MCP binary connects its server through standard input and output.
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.11.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.11 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.