bopscrk
v2.4.7 open-sourceThe section your link pointed to isn't on bopscrk's page any more, so we've brought you to the top.
Generates targeted wordlists by combining personal info, applying leet/case transforms, and fetching artist lyrics for password attacks.
extensive_case=true extensive_case=true
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
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 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 → 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 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…
Releases
8 entries
No entries match these filters.
- September 20262
- September 20241
- August 20241
- August 20221
- November 20201
- October 20202
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.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 5 of 25 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 5
- Contributors / month 0
- Commits / month 0
- Stars 1,119
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.