seclists
2026.2 open-sourceThe section your link pointed to isn't on seclists's page any more, so we've brought you to the top.
SecLists is a collection of multiple types of lists used during security assessments, including usernames, passwords, URLs, fuzzing payloads, and web shells.
Summary
seclists is an open-source collection of wordlists and payloads used during security assessments, covering usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, and web shells, free to use and pull down via git clone, a zip download, or package managers like apt on Kali and pacman on BlackArch. It is a set of files rather than a running tool, meant to sit on disk alongside scanners like Gobuster, Hydra, or Burp Suite, which read the lists as input, making it most useful to penetration testers and red teamers who need reference wordlists on a fresh testing box rather than a program to configure. Its documentation lists Assetnote Wordlists, FuzzDB, and PayloadsAllTheThings as similar projects, distinguishing itself by breadth across categories rather than automated generation. First committed in 2012, it has 367 contributors and over 1,300 commits in the past year, with a release as recently as five months ago.
SecLists is a collection of multiple types of lists used during security assessments, including usernames, passwords, URLs, fuzzing payloads, and web shells.
How seclists helps
What usernames and passwords should I try first against a login I've found?
supplies ranked credential lists, from top-used passwords to leaked-database dumps and default vendor credentials, that Hydra or a similar tool reads directly for the attempt
Which hidden directories and files might exist on this web server?
provides content-discovery wordlists like the DirBuster sets and technology-specific paths for Kubernetes, GitLab, Grafana, and similar platforms, for a scanner such as Gobuster to brute-force
Are there subdomains or DNS records I haven't found yet?
includes large subdomain wordlists, including multi-million-entry sets built from fresh Cloudflare data, for a DNS brute-forcer to check against the target domain
What credentials or endpoints are specific to the AI or API stack I'm testing?
contains dedicated lists for MCP server discovery, LLM safety-boundary testing, GraphQL and Swagger/OpenAPI endpoints, and login-bypass payloads for modern API surfaces
Would a wordlist in a language other than English catch usernames a generic list would miss?
includes locale-specific lists such as Brazilian Portuguese, Polish, and Spanish names and passwords for testing non-English-speaking targets
Languages
Command line
| 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 seclists, 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 seclists 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…
Coverage
Missing something? Tell us
What seclists connects to, runs on and detects, read from its release notes and docs. So far: 4 new detections.
4 changes, tracked since Oct 27, 2026.
-
Oct 272026
new Claude files added to quickhits.txt
feat(wordlist): Added Claude files to quickhits.txt (PR #1338)
-
Oct 272026
new LureScope observed SSH credentials wordlist
feat(wordlist): Added LureScope observed SSH credentials (PR #1342)
-
Oct 272026
new Risk-classified SQLi payload list
With SQLi payloads
feat(wordlist): Added risk-classified list of SQLi payloads
-
Oct 272026
new Template engine fuzzing wordlist
feat(wordlist): Added template engine fuzzing wordlist (PR #1340)
Nothing first seen in this window. That doesn't mean seclists shipped nothing, only that we found no record of it.
How we count
Read from 1 of 5 release notes and docs updates we hold for seclists. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through seclists's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
5 entries
No entries match these filters.
- October 20261
- March 20261
- September 20251
- April 20251
- February 20251
Project health
Issue, contributor and maintainer activity in danielmiessler/SecLists, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 26 −17 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 59% of issues opened, last 12 months
- Median time to close 1.3 days first maintainer reply 24 hours
- Open backlog 8 of 328 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 8
- Contributors / month 4
- Commits / month 5
- Stars 73,648
- bugs 15%
- features 66%
- questions 4%
- other 15%
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.