Ross ROSS = Recommend OSS · open-source software intelligence for agents

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. observed · 2026-08-28

github.com/perplexityai/bumblebee · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

76/100

  • Activity 96
  • Release rhythm 89
  • Longevity 7

Flags: young

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 26
  • age_days: 105
  • days_rel: 76
  • days_push: 26
  • n_releases_24m: 2

Full methodology

Adoption not part of the score

4975 stars · 445 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

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

cli-tool · maturity active

security developer-tools vulnerability-scanning cli security developer-tools cli supply-chain-security package-inventory sbom exposure-scanning nd mcp read-only-scanner command-line macos linux

1 source

Member repositories

RepositoryRoleHealth v2
perplexityai/bumblebeemain76

For agents

markdown · JSON · MCP: product_card(name="perplexityai/bumblebee")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem