instabox@0.8.52
A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe reviewed network, credential, and filesystem behavior supports the stated cloud CLI and onboarding flow. Runtime telemetry is disclosed and opt-out, and downloaded Windows CLI binaries are checksum-checked; native artifacts remain a review limitation.
Static reason
No blocking static signals were detected.
Trigger
A user invokes the CLI; onboarding telemetry runs after onboarding, unless disabled.
Impact
Expected cloud CLI actions and account-associated usage analytics; no automatic credential exfiltration or unrelated account action was identified.
Mechanism
The CLI communicates with the configured Instabox API, sends disclosed usage events to PostHog under stated conditions, and verifies downloaded Windows CLI binaries by checksum.
AI rationale
The reviewed network, credential, and filesystem behavior supports the stated cloud CLI and onboarding flow. Runtime telemetry is disclosed and opt-out, and downloaded Windows CLI binaries are checksum-checked; native artifacts remain a review limitation.
Evidence
~/.config/instabox/credentials.json~/.config/instabox/telemetry.json~/.claude/skills/instabox*~/.agents/skills/instabox*
Network endpoints2
api.instabox.shus.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a cloud-box CLI and its agent skills, matching the package’s stated purpose.
- The executable dispatches user-supplied commands to the bundled or installed CLI, or starts onboarding when the user invokes an onboarding command.
- Telemetry is disclosed as command names and outcomes, never arguments, and can be disabled with documented environment variables.
- Telemetry is skipped when disabled or when the configured server is not the default Instabox API; onboarding reports outcomes and runtime details using the signed-in account ID.
- The Windows CLI download path checks the downloaded binary’s SHA-256 against a valid checksum before accepting it.
- The repository-move skill tells the user that copied conversation history may contain secrets and instructs them to ask whether to skip it.
Evidence against
- Telemetry is associated with the signed-in account ID, though the package discloses the collection and provides an opt-out.
- The package ships native CLI binaries; the JavaScript review does not establish every binary’s behavior.
Behavioral surface
Source & flagged code
5 flaggedcli/instabox-windows-arm64.exeView file
•path = cli/instabox-windows-arm64.exe
kind = native_binary
sizeBytes = 8934400
magicHex = [redacted]
Medium
Ships Native Binary
Package ships native binary artifacts.
cli/instabox-windows-arm64.exeView on unpkgskills/instabox-basic-setup/scripts/install-files.pyView file
•path = skills/instabox-basic-setup/scripts/install-files.py
kind = build_helper
sizeBytes = 2977
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
skills/instabox-basic-setup/scripts/install-files.pyView on unpkgpackage.jsonView file
Findings
5 Medium7 Low
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarycli/instabox-windows-arm64.exe
MediumShips Build Helperskills/instabox-basic-setup/scripts/install-files.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencepackage.json
LowAi Review Evidencebin/instabox.mjs
LowAi Review Evidencelib/telemetry.mjs
Affected versions and remediation
This report applies to instabox@0.8.52.
See all versions of instabox for other recorded verdicts.
- Review the evidence and your use of instabox@0.8.52 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.