PAGES
← all tools
◆ Password & Credential Cracking

rling

open-source

Free plan: not checked yet · Open source: yes (from the repository)

Removes lines from files faster than rli, with deduplication, binary search, frequency analysis, and gzip support.

What you can do now

Checking Plays…

Summary

rling is an open-source command-line tool for cleaning and analyzing password wordlists, built as a faster, more memory-efficient replacement for the rli utility in hashcat-utils. It runs as a single binary that removes lines found in a reference file, deduplicates a wordlist in-place, outputs only common lines, or produces password length histograms and frequency analysis, using dynamic memory sizing and xxHashxxHashA non-cryptographic hash algorithm designed for speed, created by Yann Collet. Cyber tools use it to checksum or deduplicate large data volumes faster than MD5 or SHA without needing cryptographic guarantees.-based hashing rather than compiled-in limits. This makes it a fit for password crackers and red teamers preparing or trimming large wordlists ahead of a hashcat run rather than for general text-processing use. Its README frames it explicitly as a drop-in, much faster alternative to rli, with benchmarks showing large memory and time savings on billion-line files. First committed in 2020, it has seen 26 commits and multiple releases in the past year, the latest 49 days ago.

Removes lines from files faster than rli, with deduplication, binary search, frequency analysis, and gzip support.

How rling helps

Which entries in a giant wordlist are already in my known-password reference file?

compares the wordlist against the reference using a dynamic xxHash-backed hash table and writes out the non-matching lines, sized to the file rather than a compiled-in limit

How many unique candidate passwords do I actually have once repeats are stripped out?

dedupes the wordlist in place, reporting the count of unique lines and how many duplicates were removed

Which passwords show up in both of two large lists I'm merging?

outputs only the lines common to both files, letting the hash table size itself to whichever file is larger

What length should I target when building hashcat masks for this password set?

builds a length histogram over the wordlist and reports which lengths dominate and by what percentage

Can this reference-list comparison finish before my cracking session needs the trimmed wordlist?

runs the same removal job with multi-threaded binary search instead of full hashing, cutting time and memory on very large files at the cost of not deduplicating

all 4 features, with the evidence for each →

Languages

Not documented

Features

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

Built from rling'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 rling offers you

  • Command-line interface1

All capabilities 4 capabilities
Wordlist filtering by remove list Accepts an optional remove file and outputs only the wordlist lines that do not match entries in that file, writing results to stdout. 5 other sources · first seen Aug 2026

Also counts toward: Command-line interface

Wordlist analysis and statistics Reads a wordlist file and reports line count, duplicate detection, total byte size, character-length range, and a length-bucket histogram. 3 other sources · first seen Aug 2026
Wordlist deduplication Removes duplicate lines from a wordlist file, with options to deduplicate in-place or deduplicate and sort by line length. 2 other sources
Wordlist intersection Outputs only lines that appear in both input files, allowing common-entry extraction across two wordlists. 1 other source

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 rling, 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 rling 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

Nothing shipped since we started watching. Releases and docs updates land here as they happen.

last release Nov 13, 2026 · watching since Jun 24, 2026

Project health

Issue, contributor and maintainer activity in Cynosureprime/rling, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

  1. Contributors 1 ±0 vs prior 12 months
  2. Maintainers 1 +1 joined · −0 left, last 12 months
  3. Bus factor 1 committers behind half the commits
  4. Community-filed 100% of issues opened, last 12 months
  5. Median time to close 4.3 years first maintainer reply 18 hours
  6. Open backlog 0 of 34 issues ever filed
  1. Issues opened / month 0 · 0 communitymaintainers
  2. Open backlog 0
  3. Contributors / month 0
  4. Commits / month 0
  5. Stars 101
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 →
Saved in this browser. Sign in to sync your tools.