urlfinder
v0.0.3 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on urlfinder's page any more, so we've brought you to the top.
URLFinder is a high-speed, passive URL discovery tool that gathers URLs for web asset discovery without active scanning.
urlfinder -u company.com -fs '(company-staging.io|company.com)' -do urlfinder -u company.com -uos 'cdn\.example\.com' -uos 'analytics\.thirdparty\.io' urlfinder -u company.com -ns
What you can do now
Summary
urlfinder is an MIT-licensed open-source reconnaissance command-line tool that passively discovers URLs from curated sources, aimed at penetration testers, bug bounty hunters, and security researchers. You install it with Go or use a precompiled binary, then provide a domain or domain list; results can be written as JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory., files, or standard output for pipeline use. Its distinctive control is scope handling: regexes and fields such as registered domain or fully qualified domain name determine what it follows, excludes, or displays externally, with VirusTotal among its sources. The README shows ongoing releases.
URLFinder is a high-speed, passive URL discovery tool that gathers URLs for web asset discovery without active scanning.
How urlfinder helps
Which URLs are associated with my target domain?
passively gathers URLs from curated sources, including VirusTotal, without actively scanning the target
Which web assets can I discover without sending active scans?
collects URLs from passive sources, so the results reflect available source data rather than responses from an active probe
Which discovered URLs fall within my intended scope?
follows URLs matching supplied patterns and applies domain, registered-domain, fully qualified domain, or custom-regex scope rules
Which third-party or unrelated URLs should I exclude from my results?
filters discovered URLs using out-of-scope patterns or host-based scope settings, though excluded sources cannot appear in the final results
Which external endpoints did scoped discovery encounter?
surfaces out-of-scope endpoints found while following in-scope URLs when external results are enabled
How can I pass the discovered URLs into my existing workflow?
emits results to standard output, files, or structured JSONL, and accepts domain input from a list or pipeline; it does not validate that every URL is live
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 urlfinder, 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 urlfinder 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
2 entries
No entries match these filters.
- March 20251
- November 20241
Project health
Issue, contributor and maintainer activity in projectdiscovery/urlfinder, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed 50% of issues opened, last 12 months
- Median time to close 2.7 days first maintainer reply 2.7 days
- Open backlog 1 of 23 issues ever filed
- Issues opened / month 0 · 1 communitymaintainers
- Open backlog 1
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- 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.