----------------
🛠️ Tool
===================
Bumblebee is a read-only inventory collector targeting package, extension, and developer-tool metadata on macOS and Linux developer endpoints. It addresses a specific supply-chain response gap: when an advisory names a package or version, which developer machines currently have a matching entry in their on-disk metadata?
The problem space
SBOMs tell you what shipped. EDR tells you what ran or touched the network. But supply-chain incidents often require a third view: the messy local state spread across lockfiles, package-manager install metadata, extension manifests, and developer-tool configuration files. Bumblebee turns that scattered on-disk state into structured NDJSON component records and, when given an exposure catalog, flags exact matches for fast triage.
Technical architecture
• Single static binary, Go 1.25+, zero non-stdlib dependencies. Straightforward fleet deployment.
• Three scan profiles (baseline, project, deep) for different populations and cadences.
• Strictly read-only: no package manager execution (npm ls, pip show, go list), no source-file reads.
• MCP host configs can carry environment values and credentials in env blocks. Bumblebee parses these for server inventory but does not emit those values in output records.
Ecosystem coverage
• npm, pnpm, Yarn, Bun (via lockfiles and node_modules)
• PyPI (via dist-info/METADATA, egg-info)
• Go modules (go.sum, go.mod)
• RubyGems (Gemfile.lock, *.gemspec)
• Composer (composer.lock, installed.json)
• MCP JSON host configs (Claude Desktop, Cline, Gemini CLI/Code Assist). Non-JSON configs like Codex config.toml and Continue YAML not parsed in v0.1.
• Editor extensions: VS Code, Cursor, Windsurf, VSCodium
• Browser extensions: Chromium-family, Firefox
Self-test
bumblebee selftest runs against embedded fixtures with deliberately fake package names ([email protected]). Useful as a pre-deployment smoke test for fleet rollouts.
go install github.com/perplexityai/bumblebee/cmd/bumblebee@latest
bumblebee selftest
Known limitations
• Read-only by design: no runtime dependency or process detection
• bun.lockb presence detected but not parsed (diagnostic only)
• Non-JSON MCP configs unsupported in v0.1
• Note: haven't tested personally
🔹 tool #supplychain #SBOM #inventory #developersecurity
🔗 Source: https://github.com/perplexityai/bumblebee