registry / @bugbug-io/cli / 14.21.0
@bugbug-io/cli@14.21.0
BugBug CLI for test automation, CI workflows, and AI-agent plugin installation
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe credential flow uses BugBug’s configured API endpoint and is initiated by the user through login. Runtime telemetry is restricted to allowlisted event fields and has documented opt-outs.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI entry point starts the application; browser authorization and API operations require user commands, while documented telemetry runs when enabled.
Impact
No unauthorized credential redirection, unrelated collection, or harmful action was found.
Mechanism
Login exchanges an authorization code through the configured BugBug API and stores the returned token. Telemetry sends allowlisted event metadata to the BugBug API.
AI rationale
The credential flow uses BugBug’s configured API endpoint and is initiated by the user through login. Runtime telemetry is restricted to allowlisted event fields and has documented opt-outs.
Network endpoints2
app.bugbug.io/api/v2sentry.bugbug.io
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The published binary imports the CLI bundle as its entry point.
- The default API endpoint is BugBug’s official app service; the API client sends credentials to its configured API URL.
- Login is an explicit browser authorization flow that exchanges an authorization code, then saves the returned token.
- Telemetry limits event properties to an allowlist of scalar values, and the README documents telemetry opt-outs.
Evidence against
- Telemetry is enabled by default when a token is configured, though it can be disabled using documented settings.
- The CLI bundle initializes Sentry at startup using BugBug’s Sentry service.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
7 flaggeddist/chunk-OM7HXLEF.jsView file
6// ../../node_modules/@[redacted]-id/execAsync.js
L7: import * as child_process from "child_process";
L8: import * as util from "util";
High
Child Process
Package source references child process execution.
dist/chunk-OM7HXLEF.jsView on unpkg · L65L6: // ../../node_modules/@[redacted]-id/execAsync.js
L7: import * as child_process from "child_process";
High
bin/bugbug.mjsView file
3L4: globalThis.require = createRequire(import.meta.url);
L5:
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/bugbug.mjsView on unpkg · L3Findings
1 Critical5 High5 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/chunk-OM7HXLEF.js
HighShelldist/chunk-OM7HXLEF.js
HighCredential Redirect Persistencedist/chunk-FRVHF76K.js
HighCross File Remote Execution Contextdist/chunk-FRVHF76K.js
HighSemantic Analysis Limiteddist/getMachineId-bsd-WUTM4C2C.js
MediumDynamic Requirebin/bugbug.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
Affected versions and remediation
This report applies to @bugbug-io/cli@14.21.0.
See all versions of @bugbug-io/cli for other recorded verdicts.
- Review the evidence and your use of @bugbug-io/cli@14.21.0 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.