braa
open-sourceThe section your link pointed to isn't on braa's page any more, so we've brought you to the top.
Braa is a mass SNMPSNMPA UDP-based protocol for querying and managing network devices, standardized by the IETF. Cyber tools use it to pull interface stats, topology data, and device state from routers, switches, and servers at scale. scanner that queries dozens or hundreds of hosts simultaneously in a single process, consuming very few system resources.
Summary
braa is an open-source, free command-line mass SNMP scanner that queries hundreds of hosts simultaneously in a single process, using its own SNMP stack rather than net-snmp libraries, which keeps it fast and light on resources. It runs as a single compiled binary on Unix-like systems (Linux, FreeBSD, OpenBSD), with queries specified directly on the command line using numerical OIDs rather than named ones. This makes it a fit for network engineers and security scanners doing bulk SNMP enumeration across large address ranges rather than one-off lookups like snmpget or snmpwalk, which it explicitly contrasts itself against in its own documentation. It sits in the reconnaissance and mass-scanning space rather than offering general SNMP tooling. Development is slow but not dead: first committed in 2015 with four contributors, it saw four commits and a release in the past year, the latest 59 days ago.
Braa is a mass SNMP scanner that queries dozens or hundreds of hosts simultaneously in a single process, consuming very few system resources.
How braa helps
Which hosts across a large address range are actually answering SNMP queries?
sends the same query to every host in a specified range in one process and reports back only the ones that respond, instead of stepping through them one at a time
Which devices across a subnet share a specific configuration value, like a location string or contact name?
runs the same numerical OID query against every host in the list and lines up each host's answer, so mismatched or unexpected values stand out at a glance
What does a given OID actually return on each of these boxes, in raw form?
fetches the value and, when it is an octet string, can print it as a hexdump instead of interpreting it, so binary or non-printable data is not silently mangled
Which hosts in a range never replied to an SNMP query at all?
retries each unanswered host up to a set number of times before giving up on it, and a summary pass lists what got a response and what did not
Are the community strings I have valid across a range of devices?
lets a community string be paired with the host or host range in the query itself, so a single run can test different credentials against different segments and show which ones returned data
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 braa, 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 braa 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
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in mteg/braa, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 ±0 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 2.6 days first maintainer reply 2.6 days
- Open backlog 2 of 4 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 0
- Commits / month 0
- Stars 98
- 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.
Choose a badge style and copy the code →