PAGES
← all tools
◆ Reconnaissance & OSINT

sara

v1.4.0 open-source

Sara is a MikroTik RouterOS security inspector that detects misconfigurations, weak settings, and known CVEs via read-only SSH analysis.

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

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities · 2 backed by code, an API document or a real run

Built from sara's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • sara covers 1 of the 2 vulnerability management capabilities we track.

What sara offers you

  • Command-line interface
All capabilities 4 capabilities
RouterOS configuration profiling verified Audits selected configuration areas of a RouterOS device — such as system settings, protocols, and Wi-Fi — based on a comma-separated profile selection. 6 releases · 4 other sources · first seen Mar 2025

release

  • Adds --port flag to sara audit to target a non-standard RouterOS API port. v1.4.0 · Oct 2026 · source · release history
  • Adds sara audit <IP> <USERNAME> command that connects over the RouterOS API (api-ssl, port 8729 by default) to check MikroTik router configuration for 22 named checks (MGMT-001 through WIFI-002), each returning severity, live evidence from the router, and a RouterOS fix command.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.4.0 · Oct 2026 · source · release history
  • Adds --plaintext flag to sara audit to switch from api-ssl (port 8729) to the unencrypted api service (port 8728). v1.4.0 · Oct 2026 · source · release history
  • New audit profiles let you scope scans to system parameters only or protocol configurations only. v1.3.0 · Dec 2025 · source · release history
  • Adds scheduler analysis to surface potentially malicious scheduled tasks and hidden configuration overwrites. v1.1 · Mar 2025 · source · release history
  • Adds compromise artifact detection covering suspicious static DNS records, proxy settings, and exposed services. v1.1 · Mar 2025 · source · release history

command line

  • username_or_version — SSH username or RouterOS version string v1.3.0 · Dec 2025 · command-line history
  • profiles — Profiles: system,protocols,wifi (comma-separated) v1.3.0 · Dec 2025 · command-line history

example

  • Audit a router that exposes the API on a non-standard port, e.g. in a hardened deployment where 8729 is remapped. sara audit 192.168.88.1 sara --port 8730 v1.4.0 · Oct 2026 · source
  • Audit device with system profile sara audit 192.168.88.1 admin system
CVE-based vulnerability scanning shipped Scans for known vulnerabilities by mapping findings to CVEs based on RouterOS version. 5 releases · 1 other source · first seen Mar 2025

Shared capability: Vulnerability scanning

release

  • Adds sara cve <IP> <USERNAME> command to look up CVEs for the RouterOS version running on a connected router via the NVD API. v1.4.0 · Oct 2026 · source · release history
  • Adds sara cve --version <VERSION> to look up CVEs for any RouterOS version without connecting to a router. v1.4.0 · Oct 2026 · source · release history
  • CVE search module now supports manually specifying a RouterOS version to search against. v1.3.0 · Dec 2025 · source · release history
  • CVE report format is now more visual. v1.3.0 · Dec 2025 · source · release history
  • Adds CVE-based vulnerability scanning that maps findings to known issues by RouterOS version. v1.1 · Mar 2025 · source · release history

example

  • Look up CVEs for a specific RouterOS version without connecting to a device — useful for offline or pre-upgrade risk assessment. sara cve --version 7.14.3 v1.4.0 · Oct 2026 · source
SSH-based RouterOS connection verified Connects to a MikroTik RouterOS device over SSH using a specified IP address, port, username, and optional private key. 6 other sources · first seen Dec 2025

command line

example

  • Audit with SSH key, multiple profiles sara audit 192.168.88.1 admin system,protocols ~/.ssh/id_rsa
  • Audit with SSH key and custom port sara audit 192.168.88.1 admin system,protocols ~/.ssh/id_rsa 2222
RouterOS API-based connection shipped Connects to a MikroTik RouterOS device over the RouterOS API (librouteros), supporting both encrypted api-ssl (port 8729) and plaintext api (port 8728) services, with optional non-standard port targeting. 2 releases · first seen Oct 2026

release

  • Transport migrated from SSH (Netmiko) to the RouterOS API (librouteros); routers must now have the api-ssl service (port 8729) enabled and an account with read and api policies — SSH-based connectivity no longer works. v1.4.0 · Oct 2026 · source · release history
  • Migrates transport from SSH (Netmiko) to the RouterOS API (librouteros), dropping dependencies on python3-netmiko and python3-packaging. v1.4.0 · Oct 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

Show

3 entries

  1. October 20261
  2. December 20251
  3. March 20251
    Show

    3 entries

    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.

    1. Contributors 1 −3 vs prior 12 months
    2. Maintainers 1 +1 joined · −3 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close < 1 day first maintainer reply 6 hours
    6. Open backlog 0 of 2 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 343
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →