PAGES
← all tools
◆ Password & Credential Cracking

bopscrk

v2.4.7 open-source

Generates targeted wordlists by combining personal info, applying leet/case transforms, and fetching artist lyrics for password attacks.

Summary

bopscrk is an open-source, free command-line tool that builds targeted password wordlists by combining personal information about a target and applying case and leet-style transforms, with a lyricpass module that pulls in song lyrics tied to a given artist. It runs interactively, prompting for details about the target, or non-interactively via flags for scripted use, and it installs through pip or a git clone. It is aimed at penetration testers and red teamers doing password-cracking work who need a custom wordlist rather than a generic one, and it ships as a package in BlackArch Linux and is listed in Rawsec's Cybersecurity Inventory. First committed in 2018 and maintained by four contributors, it has had no commits in the past year and its last release was over two years ago, so it is worth checking for a fork before relying on it.

Generates targeted wordlists by combining personal info, applying leet/case transforms, and fetching artist lyrics for password attacks.

How bopscrk helps

What personal details about this target should I turn into candidate passwords?

prompts interactively for names, dates, pet names, and similar target facts, then combines every word pair up to the configured word count into candidate strings

Which case and leet variations of a guessed password should I include without listing them by hand?

applies configurable case and leet transform patterns from a config file, including an extensive mode that generates every possible case variant of each word

Can I fold an artist's song lyrics into a wordlist built for a fan or lyrics-obsessed target?

the lyricpass module searches lyrics tied to a given artist name and merges the resulting words into the combination and transform pipeline

How do I generate a wordlist for a target as part of a scripted, unattended run?

accepts a comma-separated list of words and generation limits as command-line arguments instead of prompting, so the same wordlist logic runs inside a pipeline

How long or short should the words in my generated list be?

takes minimum and maximum word-length settings and discards combined candidates that fall outside that range before they reach the output file

all 6 features, with the evidence for each →

Languages

Not documented

Features

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

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

  • Command-line interface2
All capabilities 6 capabilities
Case transformation support shipped Applies case mutations to input words during wordlist generation, with options for extensive coverage and preserving original casing. 5 releases · first seen Oct 2020

release

  • Implements extensive case transform mode for broader case mutation coverage. v2.4.7 · Sep 2024 · source · release history
  • Adds new basic case transform operations for wordlist generation. v2.4.7 · Sep 2024 · source · release history
  • Improves case transform logic to respect the original casing of input words. v2.4.7 · Sep 2024 · source · release history
  • artists and lyrics transforms are now configurable in the cfg file. v2.3 · Oct 2020 · source · release history
  • The --lyrics-all option has been removed (feature integrated in other options). v2.2 · Oct 2020 · source · release history
CLI configuration file support verified Allows users to supply a configuration file to the tool via a command-line flag. 2 releases · 1 other source · first seen Oct 2020

Also counts toward: Command-line interface

release

  • Adds --progress-bar flag to show scan progress v2.4.5 · Aug 2022 · source · release history
  • Implementations of a configuration file to store settings instead of CLI flags alone. v2.2 · Oct 2020 · source · release history

command line

Interactive mode shipped Allows users to run the tool in an interactive session rather than non-interactive batch processing. 1 release · 1 other source · first seen Aug 2024

release

  • Implements a real multiprocessing backend to increase parallelism performance. 2.4.6 · Aug 2024 · source · release history

example

  • Run interactive mode bopscrk -i
Version reporting verified Prints the tool's current version and exits when the --version flag is used. 1 release · 1 other source · first seen Aug 2022

Also counts toward: Command-line interface

release

command line

Custom charsets and transforms configuration shipped Allows the definition of custom character sets and transform patterns via a configuration file. 2 releases · first seen Oct 2020

release

  • config.yaml (cfg) allows definition of custom charsets and transform patterns. v2.3 · Oct 2020 · source · release history
  • Allows creation of custom charsets and transforms patterns through the config file. v2.2 · Oct 2020 · source · release history
Recursive leet transform support shipped Enables recursive leet speak transformations, configurable via settings. 1 release · first seen Oct 2020

release

  • Adds recursive leet transforms support, disabled by default but enableable via config. v2.2 · Oct 2020 · source · release history

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

Show

8 entries

  1. September 20262
  2. September 20241
  3. August 20241
  4. August 20221
  5. November 20201
  6. October 20202
    Show

    8 entries

    Project health

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

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 5 of 25 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 5
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,119
    Issue themes, last 12 months not measured

    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 →
    browse all tools → score card for your toolchain →