ubertooth
2020-12-R1 open-sourceThe section your link pointed to isn't on ubertooth's page any more, so we've brought you to the top.
Ubertooth is an open source wireless development platform for Bluetooth experimentation, shipping with a BLEBLEBluetooth Low Energy, a wireless protocol maintained by the Bluetooth SIG for short-range communication at minimal power draw, making it useful for cyber tools that interact with IoT devices or proximity-based systems. sniffer and Basic Rate Bluetooth Classic sniffing capability.
ubertooth-btbr ubertooth-util -x ubertooth-btle -t ubertooth-rx -d <device_id> -w capture.pcap ubertooth-dfu --write <firmware_image.dfu> --detach
Summary
ubertooth is an open-source wireless development platform, paired with its own hardware, for Bluetooth experimentation, built around a BLE (Bluetooth Smart) sniffer that can also pull data from Bluetooth Classic (BR) connections. It runs as a set of command-line tools driving a physical Ubertooth device rather than as software alone, so evaluating it means budgeting for the board as well as the code. It suits people doing hands-on Bluetooth protocol research or wireless red-teaming, such as reverse engineers and radio-security testers, rather than teams looking for a passive network monitoring service. It sits in the wireless-security category alongside other RF-analysis sniffer hardware rather than any single named competitor. Development has slowed sharply: first committed in 2010 with 53 contributors over its life, but only one commit in the past year, so treat it as mature but largely dormant.
Ubertooth is an open source wireless development platform for Bluetooth experimentation, shipping with a BLE sniffer and Basic Rate Bluetooth Classic sniffing capability.
How ubertooth helps
Which Bluetooth Low Energy devices nearby are advertising, and what are they broadcasting?
listens across the BLE advertising channels and reports each device's address and advertising data as it is captured over the air
What is actually happening inside a BLE connection between two devices I don't control?
follows the connection's channel-hopping sequence after capturing its access address, decoding link-layer packets exchanged between master and slave
Can I recover the identity of a Bluetooth Classic piconet I only see radio traffic from?
survey mode extracts the LAP and UAP address pairs from Classic BR traffic and lists the piconets it can identify without needing prior pairing information
Did a capture miss packets during a burst of activity, or can I trust the timing in this trace?
later releases fixed freezing under high traffic and corrected time discontinuities in the saved capture files, but older captures or heavy traffic can still show gaps worth checking
Can I inject or emulate a BLE peripheral to see how a central reacts?
faux slave mode lets the device answer as a BLE peripheral and transmit crafted packets, useful for probing how another device's central role behaves
Is the channel map for a connection I'm tracking still accurate after it changes mid-session?
the sniffing engine follows partial channel map updates during an active connection so tracking survives the target renegotiating its hopping pattern
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 ubertooth, 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 ubertooth 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
12 entries
No entries match these filters.
- December 20201
- December 20181
- August 20181
- June 20181
- March 20172
- October 20152
- September 20152
- February 20141
- January 20141
Project health
Issue, contributor and maintainer activity in greatscottgadgets/ubertooth, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 +1 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 407 days issues closed, last 12 months
- Open backlog 40 of 433 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 40
- Contributors / month 0
- Commits / month 0
- Stars 2,134
- other 100%
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
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.