Perplexity released Bumblebee on May 22, an open-source read-only security scanner that audits developer machines for risky packages, extensions, and AI-tool configurations. The tool is available under a permissive license on GitHub.
The product fills a specific gap. Developer workstations are an underdefended attack surface compared to production infrastructure: every CI/CD environment downstream inherits the trust posture of the laptop that pushed the commit. Recent npm and pypi supply-chain attacks (the typosquat patterns, the malicious-postinstall hooks, the AI-tool config injections that surfaced in early 2026) have all targeted the moment a developer types install. Bumblebee scans for the signatures of those attack patterns at the place they land first.
The read-only design is the key product decision. Bumblebee inspects and reports; it does not quarantine, delete, or modify anything on the user’s system. That tradeoff prioritizes developer trust over automated remediation. Developers tend to revolt against security tools that change their environments without explicit consent; a read-only scanner respects that and leaves remediation to the operator. The downside is that nothing happens unless the developer acts on the report, but Perplexity’s bet is that visibility alone is the underserved part of the problem.
The competitive position is unusual. Snyk CLI and similar tools focus primarily on project-level dependency scanning. Socket.dev runs as a paid SaaS layer over npm. The built-in npm audit covers a narrow slice of the surface. None of these targets the developer-machine layer specifically: extensions installed in VS Code or Cursor, AI tool configurations that may exfiltrate code, browser extensions that read clipboard contents. Bumblebee scans across all of those.
The structural question is why Perplexity is shipping this. Perplexity is primarily a consumer AI search product, not a security vendor. The most plausible explanation is operational: Perplexity’s own AI assistants run on developer machines (through editor extensions and CLI tools), and the company has a direct interest in those environments being trustworthy. Open-sourcing the scanner is an efficient way to harden the ecosystem the product depends on without building a paid security business as a side project.
Open-source quality and maintenance is the durability question. A read-only scanner from a non-security-focused company carries real risk of stagnation if Perplexity’s product priorities shift. The threat-detection rules need ongoing updates as new supply-chain attack patterns emerge. Without a commercial team funded to keep the rule set current, Bumblebee could fall behind the threat landscape within 12 months of release.
For engineering teams concerned about developer-machine security, Bumblebee is worth a one-hour evaluation. Install it on a representative laptop, run a baseline scan, and see what shows up. If it surfaces issues your current tooling missed, the case for integrating it into onboarding checklists and pre-commit hooks is direct. If it does not, the operational cost of running an unsupported scanner is harder to justify.
Released by Perplexity on 2026-05-22.
