# perplexityai/bumblebee

Read-only developer endpoint scanner for on-disk package, extension, and developer-tool metadata, built to check exposure to known software supply-chain compromises.

Repository: https://github.com/perplexityai/bumblebee
Canonical: https://ross.abutalabs.com/products/bumblebee
Language: Go
License: Apache-2.0
License Family: permissive
Topics: golang, package-inventory, supply-chain-security
Last push: 2026-08-07T17:19:42+00:00

## Health v2 (maintenance only)
Score: 76/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 96, release rhythm 89, longevity 7
- inputs: {"age_days": 105, "days_push": 26, "days_rel": 76, "gap_med": 26, "n_releases_24m": 2}
- flags: young
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4975, forks 445 (observed 2026-08-28T04:09:04.061271+00:00)

## What it is
Bumblebee is a read-only Go CLI that scans developer endpoints for on-disk package, extension, and developer-tool metadata (lockfiles, package-manager metadata, editor/browser extension manifests, MCP configs) and emits structured NDJSON component records. It flags exact matches against a supplied exposure catalog to answer which machines are affected by a named supply-chain compromise.

## Use cases
- check which developer machines have a compromised npm package installed
- inventory all packages and extensions on a macOS or Linux dev endpoint
- respond to a supply-chain advisory by scanning for affected versions
- find MCP server configs and agent skills across developer machines
- collect package metadata without running package managers
- audit editor and browser extension exposure after a malicious extension report

## When to choose
- you need fast, read-only exposure checks for a known compromised package or extension
- you want a single static binary with zero dependencies for endpoint inventory
- you need coverage of messy local state like lockfiles, dist-info metadata, and MCP host configs
- you are doing incident response and already know what to look for

## When to avoid
- you need full SBOM generation for shipped artifacts rather than endpoint state
- you need runtime or network behavior data, which requires EDR tooling
- you need to scan Windows endpoints
- you need vulnerability scanning with unknown-candidate discovery rather than exact-match lookups

## Facets
- artifact type: cli-tool
- maturity: active
- function: security, developer-tools, vulnerability-scanning, cli
- domain: security, developer-tools
- platform: cli
- tags: supply-chain-security, package-inventory, sbom, exposure-scanning, nd, mcp, read-only-scanner, command-line, macos, linux

## Member repositories
- perplexityai/bumblebee (main) score 76

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:04.061271+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:17:44.330862+00:00, confidence not recorded.
  - readme: https://github.com/perplexityai/bumblebee (fetched 2026-08-28T04:09:04.061271+00:00, sha 9ef979b3257d)
- Data as of 2026-08-30T08:39:29.467469+00:00.