spacecode@2.16.98
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 1d ago · by lpm-firewall-aiSource inspection found normal CLI authentication, SpaceCode API use, and user-invoked transcript summarization; it did not establish a concrete attack surface. The manifest has no install lifecycle hook, and the flagged runtime paths reviewed do not show hidden credential redirection.
Decision evidence
public snapshot- The manifest maps two CLI commands to bundled entrypoints and declares dependencies without an install lifecycle hook.
- The CLI uses SpaceCode service endpoints; its environment setup uses a supplied API key or a proxy sentinel, not the saved SpaceCode token as the proxy key.
- Login obtains a key from the SpaceCode authentication flow and stores it locally; the API client uses the configured or default SpaceCode backend.
- The REPL reads a caller-provided API key or the local SpaceCode auth file; transcript summarization sends the transcript when the user invokes compaction.
- The inspected entrypoints and required dependency files show ordinary CLI and library code; no attack behavior was established there.
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.98.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.98 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.