spacecode@2.16.88
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 1d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or confirmed credential theft. The flagged model-key behavior is caller-driven, and proxy mode uses the package's SpaceCode endpoint; the scanner similarity labels alone do not establish malicious behavior.
Decision evidence
public snapshot- The manifest defines two CLI entrypoints and contains no lifecycle script.
- The login command accepts a SpaceCode API key as an explicit command option.
- The launch flow passes a caller-provided model key into the sandbox environment; proxy mode uses a placeholder key and the SpaceCode proxy URL.
- The proxy URL belongs to SpaceCode, and telemetry sends only when a PostHog API key is present in the environment.
- Inspected dependency sources show the SDK, terminal styling, and CLI argument parsing entrypoints; no attack behavior was identified in those excerpts.
- Scanner labels report a credential redirect and known-malware similarity, but inspected source does not show an unrelated recipient receiving a caller's model credential.
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.88.
See all versions of spacecode for other recorded verdicts.
- Review the evidence and your use of spacecode@2.16.88 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.