bbot
v3.0.2 open-sourceThe section your link pointed to isn't on bbot's page any more, so we've brought you to the top.
The recursive internet scanner for hackers.
bbot -t example.com -p js-audit bbot -t www.evilcorp.com -p js-audit bbot --reset-config
Summary
bbot is an open-source reconnaissance scanner, released under AGPLv3, that automates subdomain enumeration, web scanning, email gathering, and attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. mapping from the command line, installed via pipx or Docker. Its README describes it as inspired by Spiderfoot, built for recon, bug bounties, and ASMASMAttack Surface Management: the continuous practice of discovering, inventorying, and monitoring an organization's externally exposed assets so that cyber tools can flag unknown or misconfigured entry points before attackers find them. work, which makes it a fit for red teamers, bug bounty hunters, and teams tracking their own external footprint. Scans run through modular presets covering passive and active discovery, with output modules for feeding results into systems like Elasticsearch, Kafka, or MongoDB. It targets by domain or ASNASNAutonomous System Number — a globally unique identifier assigned by regional internet registries to a network operator, letting routing protocols distinguish which organization controls a block of IP addresses. and separates targets from seeds, with a pydantic-validated config catching errors before a scan starts. First committed in 2022, it has 74 contributors, nearly 1,800 commits in the past year, and a release 31 days ago, indicating active development.
The recursive internet scanner for hackers.
How bbot helps
What subdomains exist for this domain that I haven't found yet?
combines passive API lookups with active brute-forcing and reports every subdomain discovered, with the source that found each one
Is anyone leaking API keys or tokens in the JavaScript my site ships?
runs a credential-scanning preset against every HTTP body collected from the target's web surface and tags findings with the source URL
Which of the hosts I own are actually reachable and what's running on them?
crawls from the seeds into the defined scope, resolving and probing each host, and reports live web services and open attack surface rather than just names
What email addresses and data has my organization exposed on the web?
spiders discovered sites and extracts emails and data points into a single report alongside the subdomains and hosts they came from
Did my last scan quietly change what it considers a finding?
unifies findings and vulnerabilities into one event type carrying severity and confidence, so a shift in what gets flagged shows up as a change in those fields rather than a silent gap
Are my valid credentials being accepted somewhere they shouldn't be?
runs a brute-forcing module against exposed services across the target's footprint and reports which credentials succeeded and against which host
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for bbot, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail bbot puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
9 entries
No entries match these filters.
- August 20262
- July 20262
- June 20262
- October 20253
Project health
Issue, contributor and maintainer activity in blacklanternsecurity/bbot, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 23 −2 vs prior 12 months
- Maintainers 2 +1 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 48% of issues opened, last 12 months
- Median time to close 367 days first maintainer reply 3 days
- Open backlog 20 of 1,118 issues ever filed
- Issues opened / month 0 · 1 communitymaintainers
- Open backlog 20
- Contributors / month 0
- Commits / month 0
- Stars 10,602
- bugs 52%
- features 26%
- docs 1%
- other 21%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.