Katana
v1.8.0 open-sourceThe section your link pointed to isn't on Katana's page any more, so we've brought you to the top.
Katana is a command-line web crawling tool written in Golang designed to crawl websites to gather information and endpoints.
katana -u https://app.example.com -headless -rf ./login-flow.json
katana -u https://example.com -kb -kb-secrets -kb-validate-secrets
katana -u https://example.com -pcs -pcsm tfidf -pcst 0.90
katana -u https://example.com -headless -pls networkidle
katana -u https://example.com -filter-similar -o filtered_urls.txt
katana -u https://cloud.projectdiscovery.io -headless -show-browser
katana -u https://ginandjuice.shop -headless -depth 5 -aff
katana -debug -u https://www.github.com -headless -enable-diagnostics
katana -u https://example.com -no-default-ext-filter -o results.txt
katana -silent -u https://www.google.com/appserve/security-bugs/m2/new -ot "{{email}} - {{url}}"
katana -silent -u https://scanme.sh/test/path/to/file.html -path-climb
katana -u https://example.com -td -jsonl -o results.jsonl
katana -u https://example.com -o results.txt -ncb
katana -u https://example.com -store-field url -sfd /tmp/katana-fields/
katana -u tesla.com -passive -f qurl
katana -u example.com -e 'cdn' -e 'private-ips'
katana -url https://example.com -dr
katana -fs '(company-staging.io|company.com)' -u company.com
katana -resume resume.cfg -u https://example.com
katana -u https://example.com -fdc "status_code != 200 || body_contains('error')"
katana -u https://example.com -cwu ws://localhost:9222/devtools/browser/1
katana -H headers.txt -u https://example.com -jsonl -omit-raw -omit-body
katana -iqp -u https://example.com
katana -u hackerone.com
katana -u https://example.com -r ./resolvers.txt
katana -u https://example.com -mr 'admin.*'
katana -u https://target.com -scp /usr/local/bin/chrome
katana -u https://target.com -elog katana-errors.log
katana -u https://target.com --no-sandbox
katana -u https://target.com --headless-options="--disable-gpu --window-size=1920,1080"
Summary
Katana is an open-source command-line web crawling tool written in Golang, built to enumerate URLs and endpoints across a target site, with a headless mode that renders JavaScript so single-page apps built on React or Angular get crawled properly rather than skipped. It runs from the terminal, taking input via STDIN, a single URL, or a list, and writing results to stdout, a file, or JSON, which makes it easy to slot into a larger recon pipeline. It's aimed at penetration testers, bug bounty hunters, and red teamers who need attack-surface and asset discovery ahead of deeper scanning with tools like nuclei. First committed in 2022, it now has 76 contributors and a release just 16 days ago, so development is active.
Katana is a command-line web crawling tool written in Golang designed to crawl websites to gather information and endpoints.
How Katana helps
Which endpoints and URLs does this target actually expose, including the ones a plain HTTP fetch would miss?
crawls the site in headless mode, rendering JavaScript so links, forms, and routes built by React or Angular are discovered rather than skipped
Which pages sit behind a login that a simple crawl would never reach?
carries cookies and can drive an automatic login flow so authenticated areas of the target get crawled instead of stopping at the login page
Is a JavaScript-heavy page actually finished loading before it gets crawled?
lets you switch the browser's page load strategy from a load event to waiting for network activity to settle, so content that renders late still gets captured
What hidden config, backup, or archive files is the default crawl silently throwing away?
turns off the built-in extension filter so paths normally dropped from output show up in the results
What technology stack is running behind each URL this crawl turns up?
opts into technology detection alongside the crawl so the stack behind each endpoint is recorded next to it in the JSON output
Why did a headless crawl stall or miss content on this target?
writes diagnostic information and verbose logs to a dedicated directory during the run, so the browser state at the point of failure can be inspected afterward
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 Katana, 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 Katana 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…
Commercials
pricing & packaging history · ProjectDiscovery vendor page23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
projectdiscovery.io, every changeProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
19 entries
No entries match these filters.
- October 20261
- August 20261
- May 20261
- March 20261
- January 20261
- December 20251
- August 20251
- July 20251
- December 20241
- October 20241
- March 20241
- January 20241
- September 20231
- August 20231
- June 20231
- April 20231
- March 20231
- January 20231
- November 20221
Project health
Issue, contributor and maintainer activity in projectdiscovery/katana, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 19 −3 vs prior 12 months
- Maintainers 2 +2 joined · −5 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 22% of issues opened, last 12 months
- Median time to close 276 days first maintainer reply 15 days
- Open backlog 9 of 393 issues ever filed
- Issues opened / month 0 · 1 communitymaintainers
- Open backlog 9
- Contributors / month 2
- Commits / month 8
- Stars 17,509
- bugs 13%
- features 17%
- other 70%
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
Articles
2 articles · updated Nov 4, 2026Where Katana turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 2
-
Katana: Vulnhub Walkthrough
Katana VM is made by SunCSR Team.
-
Katana: Portable Multi-Boot Security Suite
Katana is a portable multi-boot security suite which brings together many of today’s best security distributions and portable applications to run off a single Flash Drive.
1 more quote
Katana also comes with over 100 portable Windows applications; such as Wireshark, Metasploit, NMAP, Cain & Abel, and many more.
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.