@bugbug-io/cli@14.15.0
BugBug CLI for test automation, CI workflows, and AI-agent plugin installation
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest and entry point are consistent with a BugBug command-line tool, and the inspected token flow targets its configured BugBug API. The flagged process execution supports opening validated external URLs, and the manifest’s prepublishOnly script builds the package rather than running during registry installation.
Decision evidence
public snapshot- The manifest identifies this as BugBug’s CLI and exposes a single binary entry point.
- The binary shim imports the package’s built CLI entry point.
- The built-in API endpoint is BugBug’s official app host.
- The SDK uses the configured BugBug token in its Authorization header for API requests.
- The CLI can launch external URLs using platform-specific commands, a normal browser-opening capability.
- The manifest’s prepublishOnly script builds the package and is not an install-time lifecycle hook.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/chunk-OM7HXLEF.jsView on unpkg · L6Package source references dynamic require/import behavior.
bin/bugbug.mjsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @bugbug-io/cli@14.15.0.
See all versions of @bugbug-io/cli for other recorded verdicts.
- Review the evidence and your use of @bugbug-io/cli@14.15.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.