sara
v1.4.0 open-sourceThe section your link pointed to isn't on sara's page any more, so we've brought you to the top.
Sara is a MikroTik RouterOS security inspector that detects misconfigurations, weak settings, and known CVEs via read-only SSH analysis.
sara cve --version 7.14.3 sara audit 192.168.88.1 sara --port 8730
Summary
sara is an open-source command-line tool that audits MikroTik RouterOS devices for misconfigurations, weak settings, and known CVEs, connecting over SSH via Netmiko in read-only mode so a scan needs nothing more than a read-only account. It is aimed at network engineers and security professionals auditing devices they own or manage, rather than at attackers, since it performs no exploitation, bruteforcing, or configuration changes. Scans can be scoped to profiles covering system parameters, protocol settings, or wifi configuration, and a separate module checks a device's RouterOS version against known CVEs, either live or specified manually. It sits in the reconnaissance space alongside other configuration-auditing tools rather than vulnerability scanners that exploit findings. First committed in 2024, sara has had five contributors and nine commits in the past year, with its most recent release about eight months ago.
Sara is a MikroTik RouterOS security inspector that detects misconfigurations, weak settings, and known CVEs via read-only SSH analysis.
How sara helps
Which of my RouterOS devices are running a version with known CVEs?
checks the device's RouterOS version, live over SSH or manually specified, against known vulnerabilities and reports which ones apply
Which weak or risky settings exist in my system configuration?
reads the device's system parameters over a read-only SSH session and flags misconfigurations and weak settings against its checks
Are my wifi settings exposing the device to unnecessary risk?
scopes the audit to wifi configuration alone and reports weak or risky settings found there
Are my protocol configurations opening up avenues I didn't intend?
scopes the audit to protocol settings alone and reports misconfigurations found in that area
Does my router show signs of having already been tampered with?
inspects static DNS records, proxy settings, and exposed services for patterns that indicate compromise rather than just weak defaults
Could a scheduled task on my device be hiding a malicious change?
reviews scheduled tasks and configuration overwrites for entries that look planted rather than administrative
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 sara, 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 sara 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
3 entries
No entries match these filters.
- October 20261
- December 20251
- March 20251
Project health
Issue, contributor and maintainer activity in caster0x00/sara, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −3 vs prior 12 months
- Maintainers 1 +1 joined · −3 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 6 hours
- Open backlog 0 of 2 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 343
- 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
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.