bladeRF
2025.10 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on bladeRF's page any more, so we've brought you to the top.
A USB 3.0 Superspeed Software Defined Radio.
bladeRF-power --help bladeRF-update --help bladeRF-cli -i -d "*:serial=f12ce"
What you can do now
Summary
bladeRF is an open-source software-defined radio platform, covering the firmware, FPGA HDL, and host libraries needed to program and interact with bladeRF hardware over USB 3. It is operated through the bladeRF-cli command-line utility, which lists attached devices, reports firmware and FPGA versions, and flashes new firmware images, with the underlying libbladeRF library available for building custom tools on top. This suits hardware hackers and RF researchers who need direct control over signal transmission and reception rather than a packaged analysis application, and it includes bladeRF-fsk, a CPFSK modem utility for chat or file transfer between two bladeRF units at 250 kbps. It sits in the SDRSDRSoftware-defined radio: hardware that captures raw radio-frequency signals and shifts signal processing into software, letting a single device tune any frequency or protocol a program implements. hacking-hardware category alongside general-purpose radio platforms rather than any single named competitor, and having launched in 2013, it remains the active source repository behind the Nuand bladeRF hardware line.
A USB 3.0 Superspeed Software Defined Radio.
How bladeRF helps
What bladeRF hardware is actually plugged into this machine right now?
lists every attached bladeRF board it can detect over USB, so a unit that isn't enumerating shows up as missing rather than silently ignored
Is this board running firmware and FPGA images that match what I think I flashed?
reports the firmware and FPGA version actually loaded on the device, which is how a stale or mismatched image gets caught before a signal test blames the wrong layer
Can two bladeRF units exchange a file or a chat message over the air right now, without building anything?
runs a CPFSK modem link between two boards at a fixed 250 kbps raw rate, giving a working transmit/receive path to confirm before writing custom signal code
How do I get a bricked or half-flashed board back to a working state?
boots the device into the FX3 recovery mode so a firmware image can be reloaded after an interrupted upgrade
What do I build against if I want my own signal-processing tool instead of a packaged app?
exposes the same host library the command-line utility is built on, so custom tools talk to the hardware directly rather than through a fixed set of features
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 bladeRF, 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 bladeRF 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
8 entries
No entries match these filters.
- October 20251
- February 20232
- February 20211
- July 20191
- September 20181
- June 20161
- July 20151
Project health
Issue, contributor and maintainer activity in Nuand/bladeRF, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 −3 vs prior 12 months
- Maintainers 1 +0 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 93% of issues opened, last 12 months
- Median time to close 2.2 years first maintainer reply 62 days
- Open backlog 114 of 695 issues ever filed
- Issues opened / month 2 · 0 communitymaintainers
- Open backlog 114
- Contributors / month 0
- Commits / month 0
- Stars not measured
- 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.