PAGES
← all tools
◆ Reconnaissance & OSINT

uro

open-source

uro is a command-line tool that filters a URL list for security testing by removing duplicate, incremental, and low-value URLs without making HTTP requests.

source ↗ rss ↗ What is a cyber toolchain?

Summary

uro is an open-source command-line tool that takes a list of URLs and strips out the ones unlikely to matter for testing — incremental pages, blog-style content, near-duplicates that differ only by a parameter value, and static assets like images, JS or CSS. It runs as a single binary installed via pipx, reading URLs from stdin or a file and writing the filtered list back out, with whitelist, blacklist and filter flags for finer control over what survives. It is aimed at penetration testers and bug bounty hunters who pull large URL sets from crawlers and need something cheaper to work through before sending requests, since uro makes no HTTP calls itself. It sits in the reconnaissance category alongside crawling and spidering tools, handling the deduplication step those tools leave undone.

uro is a command-line tool that filters a URL list for security testing by removing duplicate, incremental, and low-value URLs without making HTTP requests.

How uro helps

Which pages in this list are blog posts or other human-written content I don't need to fuzz?

recognizes prose-style paths such as article slugs and drops them from the set that gets sent to testing

Are there URLs in here that are just images, scripts or stylesheets cluttering the target list?

removes files with known "useless" extensions like images, JS and CSS by default, so only pages worth testing remain

Do I actually want extensionless pages like a numeric identifier path kept in scope?

applies extension-based filters so pages without extensions can be kept or dropped as a group, separate from how named-extension files are handled

Which URLs came from a paginated series that all lead to the same kind of content?

detects incrementing path segments like sequential page numbers and keeps one instance instead of every page in the run

all 3 features, with the evidence for each →

Languages

Not documented

Features

3 capabilities · 3 backed by code, an API document or a real run

Built from uro's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What uro offers you

  • Command-line interface1
All capabilities 3 capabilities
Extension filtering verified Filters URLs by file extension, supporting a whitelist to keep only specified extensions (and extensionless URLs), a blacklist to remove specified extensions, and additional custom filters. 1 release · 8 other sources · first seen Apr 2023

Also counts toward: Command-line interface

release

  • Adds --whitelist and --blacklist options to keep/remove certain extensions 1.0.0-beta · Apr 2023 · source · release history

docs

  • Filters and deduplicates URL lists for security testing by removing duplicate, incremental, and uninteresting URLs.

command line

example

  • Scan only specific file types for cyber tooling vulnerabilities while ignoring others. uro --input ./repo -o results.json --whitelist '.py' --blacklist '.jpg' 1.0.0-beta · Apr 2023 · source
  • Apply multiple granular filters uro --filters hasexts hasparams
  • Blacklist specific extensions uro -b jpg png js pdf
  • Whitelist specific extensions only uro -w php asp html
URL list input verified Accepts a file containing URLs as input for processing. 1 release · 4 other sources · first seen Apr 2023

release

  • Adds -i/--input and -o/--output options to read/write to files instead of stdin/stdout 1.0.0-beta · Apr 2023 · source · release history

command line

example

  • Pipe input from a file and filter the output format for easier parsing by other cyber tooling. uro -i data.txt --filter 'strict' -o filtered_output.json 1.0.0-beta · Apr 2023 · source
  • Filter URLs from stdin cat urls.txt | uro
  • Read URLs from a file uro -i input.txt
Output file export verified Writes results to a specified output file. 1 release · 3 other sources · first seen Apr 2023

release

  • Adds -i/--input and -o/--output options to read/write to files instead of stdin/stdout 1.0.0-beta · Apr 2023 · source · release history

command line

example

  • Pipe input from a file and filter the output format for easier parsing by other cyber tooling. uro -i data.txt --filter 'strict' -o filtered_output.json 1.0.0-beta · Apr 2023 · source
  • Write filtered URLs to file uro -i input.txt -o output.txt

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for uro, 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 →

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 uro 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…

Explore the full chart →

Releases

1 entry

  1. April 20231

    1 entry

    1. 1.0.0-beta Prerelease Apr 4, 2023 · release notes

      Addition of --whitelist, --blacklist, --filter, -i/-o flags to control input/output and file extensions

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.0.0-beta https://github.com/s0md3v/uro.git
# already have the repo? check out this version:
$ git checkout 1.0.0-beta
      └──▷ USE IT
      Scan only specific file types for cyber tooling vulnerabilities while ignoring others.
      shell 
      uro --input ./repo -o results.json --whitelist '.py' --blacklist '.jpg'
      Pipe input from a file and filter the output format for easier parsing by other cyber tooling.
      shell 
      uro -i data.txt --filter 'strict' -o filtered_output.json
      • Adds --whitelist and --blacklist options to keep/remove certain extensions
      • Adds --filter option for finer control over output
      • Adds -i/--input and -o/--output options to read/write to files instead of stdin/stdout

      3 details in Everything

    Project health

    Issue, contributor and maintainer activity in s0md3v/uro, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 −3 vs prior 12 months
    2. Maintainers 0 +0 joined · −1 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 1 of 35 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 1
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,592
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback