waymore
v8.7 open-sourceThe section your link pointed to isn't on waymore's page any more, so we've brought you to the top.
waymore finds links from the Wayback Machine and other sources, and can also download archived responses to search for additional links.
waymore -i example.com -mode U --providers ghostarchive waymore -i example.com -mode R -xga waymore -i example.com --source-ip 203.0.113.42 waymore -i example.com -nt waymore -i example.com -nt waymore -i example.com -mode U -from 20230101 -to 20231231 waymore -i example.com -mode R -from 20230101 -to 20231231 -f waymore -i example.com -mode U --stream | grep '\.js' waymore -i example.com -mode U --stream -oU results.txt waymore -i example.com -xix waymore -i example.com --providers wayback,urlscan waymore -i example.com -mt application/javascript,application/json waymore -i example.com -ft image/png,image/jpeg,font/woff2
Summary
waymore is an open-source command-line tool that pulls historical URLs for a target from the Wayback Machine, Common Crawl, AlienVault OTXOTXAlienVault's Open Threat Exchange, a community platform where researchers share indicators of compromise; cyber tools integrate it to pull live threat intelligence feeds without building their own collection infrastructure., URLScan, VirusTotal and GhostArchive, and can also download the archived HTTP responses themselves so you can grep them for further links, developer comments and hidden parameters. It is built for bug bounty hunters and penetration testers doing reconnaissance, and its README positions it directly against waybackurls and gau, arguing that neither downloads archived response bodies or handles source rate limiting gracefully, which is why waymore is slow by design and tuned for coverage over speed. It runs from the terminal, storing config in a local file, and remains active, with 51 commits and 10 releases in the past year across 11 contributors.
waymore finds links from the Wayback Machine and other sources, and can also download archived responses to search for additional links.
How waymore helps
Which URLs has a target ever exposed, even ones long removed from the live site?
queries the Wayback Machine, Common Crawl, AlienVault OTX, URLScan, VirusTotal and GhostArchive together and merges the results into one deduplicated list, going back further than what the live site or a single archive shows
Which forgotten parameters or endpoints can I pull out of a target's old pages?
downloads the archived HTTP response bodies themselves, not just the URLs, so they can be grepped for extra links, developer comments and hidden parameters that never show up in a URL list alone
Am I getting a partial result set because a source throttled me without saying so?
handles the rate limiting each source imposes rather than stopping silently, and reports a per-source count of unique links contributed so a suspiciously low number is visible
Which of these archived files are actually binaries I should skip parsing as text?
inspects the actual content bytes for magic bytes before falling back to the content type header or URL extension, so binary files are saved and labeled correctly instead of being misread as HTML
Did I lose results when a connection dropped mid-crawl?
streams Wayback Machine requests so URLs already collected are saved as they come in rather than being lost if the connection is cut before the run finishes
Can I limit a recon run to what a target exposed in a specific time window?
applies the from and to date bounds across URL collection and response downloads for Wayback, Common Crawl, AlienVault OTX and VirusTotal, so the archive search can be scoped to a period around a known incident or release
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 waymore, 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 waymore 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.
- March 20262
- January 20265
- December 20254
- November 20251
- October 20251
- March 20252
- November 20241
Project health
Issue, contributor and maintainer activity in xnl-h4ck3r/waymore, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 4 +1 vs prior 12 months
- Maintainers 2 +1 joined · −0 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 17 days first maintainer reply 8.6 hours
- Open backlog 2 of 64 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 0
- Commits / month 0
- Stars 2,753
- questions 14%
- other 86%
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.