ssh-audit
v3.9.0 open-sourceThe section your link pointed to isn't on ssh-audit's page any more, so we've brought you to the top.
SSH server & client security auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
ssh-audit unix:///run/ssh-unix-local/socket ssh-audit --socks5 proxy.example.com:1080 target-host.internal ssh-audit --list-hardening-guides ssh-audit --get-hardening-guide "Debian 13" ssh-audit unix:///run/ssh-unix-local/socket ssh-audit --socks5 proxy.example.com:1080 target-host.internal ssh-audit --list-hardening-guides ssh-audit --get-hardening-guide "Debian 13" ssh-audit unix:///run/ssh-unix-local/socket ssh-audit --socks5 proxy.example.com:1080 target-host.internal ssh-audit --list-hardening-guides ssh-audit --get-hardening-guide "Debian 13" ssh-audit -T targets.txt -p 222 ssh-audit --dheat <target> NO_COLOR=1 ssh-audit <target> ssh-audit -J <target> | jq '.additional_notes' ssh-audit --manual ssh-audit target.example.com | grep sntrup761x25519-sha512@openssh.com ssh-audit --lookup RSA-SHA2-256 ssh-audit --lookup AEAD_AES_256_GCM ssh-audit -c /usr/bin/ssh ssh-audit -j example.com:22
Summary
ssh-audit is an open-source, MIT-licensed command-line tool for auditing SSH server and client configuration, run against a host or client directly from the terminal or piped through a list of targets for bulk scans. It grabs the banner, fingerprints the software and OS, and inspects key-exchange, host-key, cipher and MAC algorithms against known security history, flagging weak or backdoor-suspect choices like NIST elliptic-curve key exchanges, while policy scans check a fleet against a hardened baseline such as the built-in Ubuntu, Debian, Rocky Linux and OpenSSH guides. It suits system administrators and security engineers responsible for SSH hardening rather than broader network scanning, and its README frames it as the maintained successor to the original arthepsy/ssh-audit project after that one went inactive. With 35 contributors, 31 commits in the past year, and a release 48 days ago, it is actively maintained.
SSH server & client security auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
How ssh-audit helps
Which key-exchange and host-key algorithms on this server are weak or backdoor-suspect?
inspects the negotiated key-exchange, host-key, cipher and MAC algorithms against known security history and flags entries like NIST elliptic-curve key exchanges and their matching host keys as fail-level, suspected NSA-backdoored choices
Is this fleet still configured the way we think it is, against a hardened baseline?
runs a policy scan comparing each host's algorithm set against a built-in guide such as Ubuntu, Debian, Rocky Linux or OpenSSH and reports where a target's configuration deviates
Which of these hosts are exposed to future decryption of today's traffic?
flags every key exchange lacking post-quantum protection so encrypted sessions vulnerable to harvest-now-decrypt-later capture can be identified before hardening
What software and OS is actually answering on port 22 across my hosts?
grabs the banner from each target and fingerprints the underlying software and operating system, feeding that into the algorithm recommendations it prints
Can I audit an SSH daemon that isn't reachable over a normal network port?
connects over a UNIX socket path instead of a TCP host and port, so daemons inside containers or CI/CD pipelines can be checked without exposing a network listener
Which hosts in a mixed-port fleet still need attention when I scan them all at once?
reads a file of targets with optional per-host ports, applies a default port to any entry missing one, and reports pass/fail findings per host in one run
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 ssh-audit, 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 ssh-audit 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
16 entries
No entries match these filters.
- July 20263
- October 20241
- April 20241
- December 20231
- September 20231
- April 20231
- August 20211
- February 20211
- October 20201
- September 20201
- March 20201
- November 20192
- August 20191
Project health
Issue, contributor and maintainer activity in jtesta/ssh-audit, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 −1 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 88% of issues opened, last 12 months
- Median time to close 37 days first maintainer reply 3.9 days
- Open backlog 37 of 280 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 37
- Contributors / month 0
- Commits / month 0
- Stars 4,297
- 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.