registry / @codemarc/blt / 1.11.1
@codemarc/blt@1.11.1
blt cli
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged behavior is connected to explicit CLI operations: DigitalOcean credentials go to DigitalOcean, while payment secrets are deployed through the Supabase secrets command. The added device launcher validates its URL and stores configuration locally; no unrelated collection or automatic attack behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User invokes the relevant DigitalOcean, Supabase deployment, or device command.
Impact
Expected infrastructure management, secret deployment, or local device-browser setup.
Mechanism
Commands use service-specific credentials with their respective APIs, deploy selected secrets to Supabase, or save device configuration and launch a browser.
AI rationale
The flagged behavior is connected to explicit CLI operations: DigitalOcean credentials go to DigitalOcean, while payment secrets are deployed through the Supabase secrets command. The added device launcher validates its URL and stores configuration locally; no unrelated collection or automatic attack behavior was found.
Evidence
~/.blt/devices/<name>/device.json~/.blt/devices/<name>/profile
Network endpoints2
api.digitalocean.com/v2supabase.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The CLI entry point registers commands and runs the command parser; it does not invoke the flagged helpers directly.
- The DigitalOcean helper reads DigitalOcean-specific tokens and sends them as bearer authorization to api.digitalocean.com.
- The droplet creation flow is exposed through the explicit spin-up operation and uses the token for DigitalOcean account operations.
- The secrets command is explicitly invoked as `deploy secrets` and sets Stripe or Square secrets in Supabase.
- Device pairing requires a user-provided application URL and launches the selected browser with a local device profile.
Evidence against
- The static scanner flagged credential handling, shell execution, and newly added device-launch code; inspection ties these to CLI features rather than an automatic attack.
- The launcher validates HTTPS or localhost URLs, writes a restrictive local configuration, and starts the browser without a shell.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
Source & flagged code
4 flaggeddist/lib/github.jsView file
1import { spawnSync } from "node:child_process";
L2: export function ensureGhInstalled(logger) {
High
dist/lib/digitalocean.jsView file
4import { homedir } from "node:os";
L5: const DO_API = "https://api.digitalocean.com/v2";
L6: function readDoctlToken() {
L7: const configPath = process.platform === "darwin"
L8: ? join(homedir(), "Library", "Application Support", "doctl", "config.yaml")
L9: : join(homedir(), ".config", "doctl", "config.yaml");
...
L19: function getToken() {
L20: const token = process.env.DIGITALOCEAN_ACCESS_TOKEN ??
L21: process.env.DIGITALOCEAN_TOKEN ??
...
L39: return undefined;
L40: const body = await res.text();
L41: if (!res.ok) {
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/lib/digitalocean.jsView on unpkg · L4Findings
1 Critical4 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/device/launcher.js
HighChild Processdist/lib/github.js
HighShell
HighSandbox Evasion Gated Capabilitydist/lib/digitalocean.js
HighRuntime Package Installdist/commands/deploy/functions.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @codemarc/blt@1.11.1.
See all versions of @codemarc/blt for other recorded verdicts.
- Review the evidence and your use of @codemarc/blt@1.11.1 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.