spacecode@2.16.25
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiSource inspection resolves the credential-routing signal to normal SpaceCode authentication: the API base defaults to SpaceCode’s backend, and login keys come from user input or the SpaceCode device flow. The manifest has no lifecycle hook, and the similarity label alone does not establish malicious behavior.
Decision evidence
public snapshot- The package manifest identifies the CLI entrypoints and contains no lifecycle hook; the main binary and MCP binary were inspected.
- The CLI takes API keys from login input or the device login flow, stores them locally, and sends bearer credentials to its configured API base, whose default is SpaceCode’s backend. The auth flow defaults to SpaceCode’s app host.
- Telemetry is gated by an environment-provided PostHog key and defaults to the PostHog host.
- The inspected dependency excerpts show protocol, validation, terminal styling, and CLI modules; the MCP entrypoint starts a stdio server.
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.25.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.25 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.