changeme
v1.2.3 open-sourceThe section your link pointed to isn't on changeme's page any more, so we've brought you to the top.
changeme is a default credential scanner that detects default and backdoor credentials across protocols including HTTP, SSH, FTP, 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., and databases.
changeme --all <target>
Summary
changeme is an open-source command-line scanner that checks hosts and networks for default and backdoor credentials, free to use. It runs from the command line, taking a single host, a subnet, an nmap XML file, or a Shodan query as its target, and it checks HTTP/HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate., SSH, SNMP, FTP, and databases like MySQL, MSSQL, MongoDB and Postgres, with credentials stored in editable YAML files rather than code. It suits penetration testers and red teamers who need to catch default-credential exposures a commercial scanner might skip. The README describes it as picking up where commercial scanners leave off, placing it as a complement to those tools rather than a replacement. First committed in 2016 with 23 contributors and 10 tracked releases, the project has seen no commits in the past year.
changeme is a default credential scanner that detects default and backdoor credentials across protocols including HTTP, SSH, FTP, SNMP, and databases.
How changeme helps
Which devices on my network are still using the credentials they shipped with?
tries known default and backdoor username/password pairs against every host it is pointed at over HTTP, SSH, SNMP, FTP, and common databases, and reports which ones let it in
Which hosts from my last nmap sweep are worth a closer look for weak logins?
reads the scan file directly, targeting the hosts and ports it already found rather than rescanning the network from scratch
Did a commercial scanner already flag everything I need to worry about?
checks specifically for default and backdoor credentials, a narrower and often skipped category, so it can turn up exposures a general-purpose scanner passed over
Is a device reachable over SSH still sitting on a known vendor key instead of a unique one?
tests the host against a set of previously disclosed SSH keys in addition to password guesses, and reports a match by host
Can I add a newly disclosed default password without waiting on the maintainers?
credentials live in editable YAML files rather than in code, so a new entry can be added and picked up on the next run without touching the scanner itself
Are the credential definitions I'm relying on still correctly formed?
offers a validation pass over the YAML credential files that flags malformed entries before they're used in a scan
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 changeme, 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 changeme 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
6 entries
No entries match these filters.
- April 20201
- March 20182
- September 20171
- March 20172
Project health
Issue, contributor and maintainer activity in ztgrace/changeme, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±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 not measured issues closed, last 12 months
- Open backlog 15 of 60 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 15
- Contributors / month 0
- Commits / month 0
- Stars 1,517
- 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.No high or critical advisory in the lockfiles we checked.
We check the lockfiles its release builds images from: 1 Python. Go modules, other lockfiles and vendored code aren't checked.
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 →