bettercap-ui
v1.4.0 open-sourceThe section your link pointed to isn't on bettercap-ui's page any more, so we've brought you to the top.
Official web UI for bettercap, the network attack and monitoring framework.
Summary
bettercap-ui is an open-source, GPL 3-licensed web interface for bettercap, the network attack and monitoring framework, giving it a browser-based dashboard instead of the raw command-line syntax bettercap normally requires. It is built as a submodule of bettercap itself, compiled from source alongside it or installed from a published release artifact, and served locally as the framework's web UI rather than run as a separate standalone service. This suits penetration testers and red teamers already using bettercap for MITM and WiFi work who want a visual layer for tasks like pulling captured WiFi handshakes or monitoring CAN bus events without memorizing its scripting interface. Its README frames it strictly as bettercap's official companion rather than a competitor to other tools. Development has slowed: eight contributors since 2018, seven tracked releases, but no commits in the past year and the last release over a year old.
Official web UI for bettercap, the network attack and monitoring framework.
How bettercap-ui helps
Which devices on this network are visible to bettercap right now, and what is happening to them?
shows the framework's live host and event state in a browser dashboard, so MITM targets, WiFi access points, and traffic events appear visually instead of scrolling through terminal output
Which WiFi handshakes have been captured during an assessment, and how do I get them off the box?
lists captured handshakes with a red key icon that downloads the file directly, without needing to locate it on disk or use a separate command
What is happening on a CAN bus session as it runs?
renders CAN bus events and icons in the same interface, so message activity can be watched as it happens instead of read from raw log lines
Can I tell whether an SSL warning during a MITM session is something to worry about?
surfaces the warning as a dismissable dialog in the UI, flagging it without interrupting the session, though judging its significance is left to the operator
Is the machine I'm pointing my browser at actually running the same UI I built or downloaded?
serves the interface locally as part of the bettercap process itself, so what loads in the browser reflects whatever version was compiled or installed alongside that framework instance
Languages
Command line
| 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 bettercap-ui, 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 bettercap-ui 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
5 entries
No entries match these filters.
- August 20251
- May 20191
- April 20191
- March 20192
Project health
Issue, contributor and maintainer activity in bettercap/ui, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 −1 vs prior 12 months
- Maintainers 0 +0 joined · −1 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 not measured issues closed, last 12 months
- Open backlog 2 of 39 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 0
- Commits / month 0
- Stars 369
- 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.