PAGES
← all tools
◆ Password & Credential Cracking

brutespray

v2.7.2 open-source

Fast, multi-protocol credential brute-forcer. Parses Nmap, Nessus, and Nexpose output to automatically test default and custom credentials across 30+ protocols.

Summary

brutespray is an open-source, free command-line tool that takes scan output from Nmap, Nessus, Nexpose, or JSON and brute-forces credentials against discovered services across 41 protocols in parallel. It runs as a Go binary with an interactive terminal UI, embedded wordlists, and resume/checkpoint support, and it fits naturally into recon pipelines, accepting piped input from tools like naabu or fingerprintx. It's built for penetration testers and red teamers who need to move from a network scan straight to credential validation, with lockout-aware spray modes and SOCKS5SOCKS5A proxy protocol that relays TCP and UDP traffic through an intermediary server without inspecting it, letting cyber tools tunnel connections through firewalls or pivot hosts with minimal overhead. proxy support for engagement-safe pacing. It sits in the password-cracking category alongside tools like Hydra and Medusa, but centers on parsing scanner output rather than raw target lists. Started in 2017, it remains actively developed, with 215 commits and 21 releases in the past year and a release just 54 days ago.

Fast, multi-protocol credential brute-forcer. Parses Nmap, Nessus, and Nexpose output to automatically test default and custom credentials across 30+ protocols.

How brutespray helps

Which credentials actually work on the services this scan just found?

reads the Nmap, Nessus, Nexpose, JSON, or list output and runs matching protocol modules with the given user/password sources in parallel, reporting which host/service pairs authenticated successfully

Which of my SSH hosts are still sitting on known-bad or vendor default keys?

checks each host against an embedded corpus of known-bad keys before any password spraying, flagging matches with CVE-tagged metadata so exposure shows up without a single guessed password

Am I about to lock accounts out by spraying too aggressively?

offers a lockout-aware spray mode with configurable delay between attempts so a slow, deliberate pace can be set instead of hammering every credential at once

Which of my Windows RDP hosts are exposed to the Sticky-Keys backdoor?

performs pre-authentication RDP reconnaissance that fingerprints whether network-level authentication is enforced and checks for the sticky-keys backdoor pattern without needing valid credentials first

Did a run stall out on dead hosts instead of finishing the live ones?

lets the queue order prioritize responsive hosts and skip services after repeated connection failures, so a scan doesn't dwell on unreachable targets while live ones wait

Can I pick a spray back up after stopping it midway through a large target list?

checkpoints progress per host and resumes from where it left off, using a count-based cursor to skip credential pairs already attempted on partially completed hosts

all 23 features, with the evidence for each →

Languages

Not documented

Features

23 capabilities across 6 areas · 8 backed by code, an API document or a real run

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

  • Command-line interface11
  • JSON data export2
  • CI/CD pipeline integration1
Credential Attack Execution 3 capabilities Controls how credentials are tried against target hosts, including the order, scheduling mode, and behaviour when connections fail or hosts appear to lock out. This is the core function the cyber tool is built around.
Credential queue scheduling verified Lets the user choose how credentials are distributed across hosts, for example spraying one password across all hosts before moving to the next. 2 releases · 4 other sources · first seen Jun 2026

release

  • Adds --schedule auto|host-major|spray|pairwise to select deterministic credential queue ordering. v2.6.3 · Jun 2026 · source · release history
  • Adds --schedule auto|host-major|spray|pairwise to control credential queue ordering for deterministic or spray-style execution. v2.6.3 · Jun 2026 · source · release history

command line

  • --schedule — Credential queue schedule: auto, host-major, spray, pairwise (deterministic execution also needs -t 1 -T 1) v2.6.3 · Jun 2026 · command-line history

example

  • Use combo credentials on SSH host brutespray -H ssh://10.0.0.1:22 -C root:root
  • Target specific SSH host with password list brutespray -H ssh://192.168.1.1:22 -u admin -p passlist.txt
  • Spray credentials over CIDR range brutespray -H ssh://10.1.1.0/24:22 -u root -p passlist.txt
Machine-readable attempt status codes shipped Produces a consistent, machine-readable status code for every attempt outcome so results can be parsed reliably downstream. 5 releases · first seen Mar 2026

Also counts toward: Command-line interface

release

  • Adds evidence modes full, redacted, hash, and reserved encrypted for machine-readable credential output; hash mode emits HMAC-SHA256 correlation values without printing the secret. v2.7.2 · Aug 2026 · source · release history
  • Adds module boundary protection: panicking modules are caught and recorded as module_panic_recovered; hung modules are capped and recorded as module_timeout. v2.6.3 · Jun 2026 · source · release history
  • JSONL attempt output now includes an additive status_code field alongside the legacy status field. v2.6.3 · Jun 2026 · source · release history
  • Introduces stable machine-readable attempt status codes (auth_success, auth_failure, connection_failure, unsupported_service, module_timeout, module_panic_recovered, skipped_service) propagated through JSONL output, session logs, and TUI. v2.6.3 · Jun 2026 · source · release history
  • Enables automatic CSRF token extraction for HTTP-form attacks via -m csrf:FIELD_NAME. v2.6.0 · Mar 2026 · source · release history
Host-skip and connection-failure policy verified Automatically skips a host or service after a configurable number of consecutive connection failures, reducing noise against unresponsive targets. 1 release · 4 other sources · first seen Jun 2026

release

  • Adds --skip-policy auto|off|conservative|aggressive and --max-conn-fails to tune when repeated connection failures cause a host/service to be skipped. v2.6.3 · Jun 2026 · source · release history

command line

  • --skip-policy — Connection-failure skip policy: auto, off, conservative, aggressive v2.6.3 · Jun 2026 · command-line history
  • --max-conn-fails — Consecutive connection failures before skip policy trips (0 = policy default) v2.6.3 · Jun 2026 · command-line history

example

  • Use a host-major queue order with aggressive connection-failure skipping to finish live hosts first and avoid dwelling on dead ones. brutespray -f targets.gnmap --schedule host-major --skip-policy aggressive --max-conn-fails 3 -u users.txt -p passwords.txt v2.6.3 · Jun 2026 · source
  • Tune host-skip behaviour during a large scan so aggressive connection failures don't stall a run, while keeping spray-mode lockout awareness intact. brutespray -f nmap.gnmap --skip-policy aggressive --max-conn-fails 3 -u admin -p passlist.txt v2.6.3 · Jun 2026 · source
Run Management and Recovery 2 capabilities Tracks progress across a run so that interrupted sessions can be restarted without repeating work already done. It also isolates faults in individual protocol modules so a single failure does not abort the entire run.
Resume cursor for interrupted runs shipped Records how far through the credential queue each host has been processed so a restarted run picks up where it left off. 4 releases · first seen Mar 2026

Also counts toward: Command-line interface

release

  • Adds granular count-based per-host resume cursor so interrupted runs skip already-attempted queue prefixes on partially completed hosts. v2.6.3 · Jun 2026 · source · release history
  • Ctrl+C now prints the exact --resume command needed to continue a session later. v2.5.5 · Mar 2026 · source · release history
  • Session replay on --resume: the full previous session is replayed into the TUI so the scan appears uninterrupted. v2.5.5 · Mar 2026 · source · release history
  • Resume/checkpoint support: automatically saves progress on Ctrl+C; resume with -resume. v2.5.4 · Mar 2026 · source · release history
Module fault isolation shipped Catches crashes or hangs inside individual protocol modules and records them as recoverable outcomes rather than stopping the whole run. 2 releases · 1 other source · first seen Mar 2026

Also counts toward: Command-line interface

release

  • Adds module boundary protection: panicking modules are caught and recorded as module_panic_recovered; hung modules are capped and recorded as module_timeout. v2.6.3 · Jun 2026 · source · release history
  • New default interactive TUI (Bubble Tea) with tabbed views: All, By Host, By Service, Completed, Successes, Errors, Settings; use --no-tui to revert to legacy output. v2.5.4 · Mar 2026 · source · release history

example

  • Run a spray attack against a target list with a delay between attempts to avoid lockouts, saving a checkpoint you can resume if interrupted. brutespray -f targets.xml -spray -spray-delay 2s -resume v2.5.4 · Mar 2026 · source
Diagnostics and Observability 2 capabilities Provides detailed logging and routing information to help operators verify what the cyber tool is doing and audit completed runs. Output is structured to support post-engagement review without exposing sensitive credential material in logs.
Per-attempt diagnostic audit logging verified Writes a per-attempt log file in JSONL format with passwords removed, giving a reviewable audit trail without storing cleartext credentials. 6 releases · 3 other sources · first seen Aug 2025

Also counts toward: JSON data export

release

  • Adds brutespray audit verify subcommand requiring BRUTESPRAY_AUDIT_HMAC_KEY; missing or incorrect keys fail verification with a fail-closed exit. v2.7.2 · Aug 2026 · source · release history
  • brutespray audit verify requires the BRUTESPRAY_AUDIT_HMAC_KEY environment variable; missing or incorrect keys cause verification to fail. v2.7.2 · Aug 2026 · source · release history
  • Adds brutespray audit verify subcommand for authenticated audit chain verification requiring BRUTESPRAY_AUDIT_HMAC_KEY v2.7.2 · Aug 2026 · source · release history
  • Adds authenticated audit chains using HMAC-SHA256 chaining instead of a recomputable plain hash; sensitive artifacts (checkpoints, session logs, stores, audit files) use owner-only permissions. v2.7.2 · Aug 2026 · source · release history
  • Adds --debug-audit and --debug-file to write per-attempt JSONL diagnostics with passwords and credential substrings redacted. v2.6.3 · Jun 2026 · source · release history
  • Adds no-color output option for clean logging in CI/CD pipelines and log aggregation. v2.4.0 · Aug 2025 · source · release history

command line

  • --debug-file — Debug audit JSONL path (default: brutespray-debug.jsonl) v2.6.3 · Jun 2026 · command-line history

example

  • Write redacted per-attempt diagnostics to disk for post-engagement review without exposing raw passwords in logs. brutespray -f nmap.gnmap -u root -p passlist.txt --debug-audit --debug-file audit.jsonl v2.6.3 · Jun 2026 · source
  • Run a brute force campaign in CI with no-color output for clean log ingestion. brutespray -f nmap.xml -s ssh -U users.txt -W passwords.txt --no-color | tee brutespray.log v2.4.0 · Aug 2025 · source
Route diagnostics verified Shows which network interface, local IP, and proxy the cyber tool is using for each target so the operator can confirm traffic is routed correctly before or during a run. 3 releases · 1 other source · first seen Jan 2025

Also counts toward: Command-line interface

release

  • Adds --route-diagnostics to print selected interface, bound local IP, and proxy context per target (disables TUI so output stays visible). v2.6.3 · Jun 2026 · source · release history
  • Adds SOCKS5 proxy support for routing credential-spray traffic through a proxy. v2.3.1 · Jan 2025 · source · release history
  • Adds interface selection option to control which network interface is used for connections. v2.3.1 · Jan 2025 · source · release history

command line

  • --route-diagnostics — Print selected local route/source address per target v2.6.3 · Jun 2026 · command-line history
Target and Protocol Reconnaissance 2 capabilities Helps operators understand what protocols and modules are available and how a specific target may already be compromised before attempting credentials. This informs planning decisions ahead of an active run.
Protocol module introspection verified Displays a protocol module's default port, credential requirements, and available options so the user can confirm correct configuration before targeting it. 1 release · 2 other sources · first seen Jun 2026

Also counts toward: Command-line interface

release

  • Adds --module-help <service|all> to introspect default port, credential mode, module params, and wrapper gating for any protocol module. v2.6.3 · Jun 2026 · source · release history

command line

  • --module-help — Print module defaults and accepted module params for a service or all v2.6.3 · Jun 2026 · command-line history

example

  • Inspect a protocol module's default port, credential mode, and accepted params before targeting it. brutespray --module-help rdp v2.6.3 · Jun 2026 · source
RDP sticky-keys detection shipped Detects whether a Windows RDP target has a sticky-keys accessibility backdoor active at the login screen, indicating prior compromise. 1 release · first seen Jun 2026

release

  • Enhances RDP sticky-keys detection with broader detectTerminalWindow logic covering cmd.exe, PowerShell, and custom shell colors. v2.6.3 · Jun 2026 · source · release history
Wordlist and Research Support 1 capability Assists with building or refining the credential lists used during an engagement. The cyber tool connects to a configured LLM endpoint to support wordlist research tasks.
AI-assisted wordlist research shipped Queries a configured AI language model to help the user research and develop wordlists for use in credential attacks. 1 release · first seen Jun 2026

release

  • Supports OpenAI-compatible endpoints (e.g. vLLM) for wordlist research via WORDLIST_RESEARCH_PROVIDER, WORDLIST_RESEARCH_MODEL, and WORDLIST_RESEARCH_URL environment variables. v2.6.3 · Jun 2026 · source · release history
Other 13 capabilities
Protocol support expansion shipped Adds discovery and service mapping capabilities for XMPP, TeamSpeak, and Oracle DB protocols. 14 releases · 2 other sources · first seen Feb 2024

release 14 total

  • Adds five new database brute-force modules: CouchDB (5984), Elasticsearch (9200), InfluxDB (8086, v1/v2 via -m mode:v1), Neo4j (7687, Bolt v5), and Cassandra (9042, CQL native), bringing total service count to 41. v2.6.2 · May 2026 · source · release history
  • Adds 12 new service modules: SVN, SOCKS5-auth, HTTP-form, HTTPS-form, SMTP-VRFY, rexec, rlogin, rsh, wrapper, FTPS, LDAPS — bringing the total to 35+. v2.6.0 · Mar 2026 · source · release history
  • Supports multi-auth auto-detection: HTTP Digest/NTLM, SMTP PLAIN/LOGIN/NTLM, IMAP CRAM-MD5, POP3 APOP (from banner), and SMB pass-the-hash. v2.6.0 · Mar 2026 · source · release history
  • Telnet module now recognizes login/password prompts in 10 languages including Chinese, Japanese, Korean, and Russian. v2.6.0 · Mar 2026 · source · release history
  • New LDAP and LDAPS bruteforce module. v2.5.4 · Mar 2026 · source · release history
  • New WinRM bruteforce module. v2.5.4 · Mar 2026 · source · release history

example

  • Throttle SSH brute-force to one attempt every 10 seconds to evade rate-limiting or lockout policies, without calculating a fractional rate. brutespray -file nmap.xml -service ssh -delay 10s v2.6.1 · May 2026 · source
  • Target specific services including newly supported protocols like XMPP and Oracle DB. brutespray -f hosts.txt -s xmpp,oracle_db,teamspeak v2.2.1 · Feb 2024 · source
Connection management shipped Manages concurrent service connections and threading architecture to control parallelism and stability. 8 releases · 2 other sources · first seen Jan 2025

release 8 total

  • Adds lockout_threshold, lockout_window, safe_margin, and jitter_percent policy controls in engagement manifests for lockout-aware attempt budgets, with shared scheduling across worker pools. v2.7.2 · Aug 2026 · source · release history
  • Adds allow/deny scope controls — host and CIDR allowlists plus explicit deny rules applied before execution; rejected targets appear in dry-run output with stable reasons. v2.7.2 · Aug 2026 · source · release history
  • Normalizes lockout-budget account identities to service|domain|user across worker pools instead of resetting per goroutine. v2.7.2 · Aug 2026 · source · release history
  • Introduces --proxy-list for round-robin rotation across multiple SOCKS5 proxies. v2.6.0 · Mar 2026 · source · release history
  • Live-adjustable threads-per-host and parallel-hosts settings during an active scan via the TUI Settings tab. v2.5.4 · Mar 2026 · source · release history
  • SOCKS5 proxy support routed through a centralized ConnectionManager for all modules. v2.5.4 · Mar 2026 · source · release history

example

  • Enforce scope limits and define lockout policies in an engagement manifest file. # engagement.yaml # scope: # allow: [10.0.0.0/8] # deny: [10.0.1.50/32] # lockout_policy: # threshold: 5 # window: 300 # evidence: # hmac_key: 'supersecretkey' v2.7.2 · Aug 2026 · source
  • Rotate through multiple SOCKS5 proxies round-robin to distribute spray traffic across exit nodes. brutespray -f hosts.gnmap -s ssh -U users.txt -P passwords.txt --proxy-list proxies.txt v2.6.0 · Mar 2026 · source
Dry-run planning and review verified Resolves targets and credentials into a deterministic JSON execution plan without performing authentication attempts, supporting output to file for review or CI gating. 3 releases · 2 other sources · first seen Aug 2026

Also counts toward: Command-line interface, JSON data export

release

  • Adds --dry-run flag to resolve targets and credentials into deterministic JSON without performing any authentication attempts. v2.7.2 · Aug 2026 · source · release history
  • Adds --dry-run, --plan-out, and --require-plan-ack flags to resolve targets/credentials into a deterministic JSON execution plan without performing authentication attempts v2.7.2 · Aug 2026 · source · release history
  • Adds --plan-out flag to write the full execution plan to a file for review, approval, or CI evidence. v2.7.2 · Aug 2026 · source · release history

command line

  • --dry-run — Resolve targets and credentials into an execution plan without attempting logins v2.7.1 · Aug 2026 · command-line history
  • --plan-out — Write dry-run execution plan JSON to this file v2.7.1 · Aug 2026 · command-line history
Pipeline input support shipped Automatically detects and ingests structured scan data from standard tools via stdin to facilitate chaining with other cyber tooling. 2 releases · 2 other sources · first seen May 2026

Also counts toward: Command-line interface

release

  • Adds --debug-audit and --debug-file flags to write per-attempt JSONL diagnostics with passwords redacted and credential substrings scrubbed from error text. v2.6.3 · Jun 2026 · source · release history
  • Adds stdin pipeline ingestion: auto-detects naabu, Nerva URI/JSON, fingerprintx JSON, and masscan -oJ formats when no -f or -H is supplied, enabling chains like naabu | fingerprintx | brutespray. v2.6.2 · May 2026 · source · release history

docs

  • Brute-forces credentials across 40+ protocols using Nmap, Nessus, Nexpose, JSON, or list input with an interactive TUI.

example

  • Brute-force from Nmap GNMAP output brutespray -f nmap.gnmap -u admin -p password
Engagement manifest support verified Loads YAML configuration files for engagement identity, scope controls (allow/deny), lockout policies, and evidence defaults. 2 releases · 1 other source · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Adds engagement manifests (YAML) carrying engagement identity, authorization references, scope, lockout policy, and evidence defaults. v2.7.2 · Aug 2026 · source · release history
  • Adds YAML engagement manifests supporting evidence.hmac_key, allow/deny scope controls, and lockout policy configuration v2.7.2 · Aug 2026 · source · release history

command line

  • --engagement — Engagement manifest YAML with scope, policy, and evidence defaults v2.7.1 · Aug 2026 · command-line history
InfluxDB v2 token mode shipped Adds specific credential routing for InfluxDB v2 that attempts tokens once per token without multiplication across default usernames. 2 releases · first seen Aug 2026

release

  • Adds token-aware execution for InfluxDB v2 — tokens are attempted once per token without multiplication across default usernames; use -m mode:v1 to preserve username/password pair generation. v2.7.2 · Aug 2026 · source · release history
  • Adds InfluxDB v2 token mode as default credential routing (use -m mode:v1 for v1 username/password pairs) v2.7.2 · Aug 2026 · source · release history
Plan acknowledgment security verified Enforces engagement manifest requirements and HMAC-based plan hashing to prevent credential substitution between review and execution. 1 release · 1 other source · first seen Aug 2026

release

  • --require-plan-ack requires an engagement manifest containing evidence.hmac_key to proceed with execution v2.7.2 · Aug 2026 · source · release history

command line

  • --require-plan-ack — Require acknowledgment of the exact plan hash before execution v2.7.1 · Aug 2026 · command-line history
Inline credential input shipped Accepts credential pairs directly via command-line flags for quick testing or pipeline integration without requiring external files. 1 release · 1 other source · first seen May 2026

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Adds -c/--creds flag for inline credential pairs ('user:pass,user2:pass2') without requiring a file. v2.6.2 · May 2026 · source · release history

example

  • Brute-force multiple services using inline credential pairs without creating a file, slotting into a live recon pipeline. naabu -p 5984,9200,8086 -host 10.0.0.0/24 | fingerprintx | brutespray -c 'admin:admin,root:changeme,elastic:' v2.6.2 · May 2026 · source
Pre-authentication reconnaissance shipped Performs lightweight discovery checks, such as bad SSH key verification and RDP NLA fingerprinting, before initiating credential attacks. 2 releases · first seen May 2026

release

  • Adds pre-auth RDP recon (brute.ScanRDPRecon): X.224 NLA fingerprinting without authentication, plus sticky-keys backdoor detection (T1546.008) when NLA is not enforced; disable with --no-rdp-scan. v2.6.2 · May 2026 · source · release history
  • Adds SSH bad-keys pre-pass: embedded Rapid7 ssh-badkeys corpus (plus Vagrant, F5, Barracuda, and others) compiled into the binary, with CVE-tagged metadata and BADKEY/type:badkey output; controlled via --no-badkeys and --badkeys-only. v2.6.2 · May 2026 · source · release history
Rate limiting and throttling shipped Controls the speed of authentication attempts per host or globally using either fractional rate values or explicit delay durations. 1 release · 1 other source · first seen Mar 2026

release

example

  • Throttle SSH brute-force to one attempt every 10 seconds to evade rate-limiting or lockout policies, without calculating a fractional rate. brutespray -file nmap.xml -service ssh -delay 10s v2.6.1 · May 2026 · source
Resume and interruption handling shipped Captures session state to allow interrupted runs to be resumed from the exact point of termination, with CLI help for the resume command. 2 other sources · first seen Mar 2026

Also counts toward: Command-line interface

example

  • Run a spray attack against a target list with a delay between attempts to avoid lockouts, saving a checkpoint you can resume if interrupted. brutespray -f targets.xml -spray -spray-delay 2s -resume v2.5.4 · Mar 2026 · source
  • Resume a previously interrupted scan — Ctrl+C now prints the exact command; pass either the .json or .jsonl session file and brutespray resolves it automatically. brutespray --resume session.jsonl v2.5.5 · Mar 2026 · source
Canonical service descriptor registry shipped Maintains a central registry of default ports, aliases, credential modes, routing support, and stability metrics for protocol modules. 1 release · first seen Aug 2026

release

  • Adds a canonical service descriptor registry covering default ports, aliases, credential modes, routing support, module parameters, stability, and wordlist aliases. v2.7.2 · Aug 2026 · source · release history
Durable engagement record storage shipped Stores engagement records in a JSONL workspace without requiring an external database, providing commands for initialization and inspection. 1 release · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Adds JSONL workspace store for durable engagement records without requiring CGO or an external database, with new workspace command paths for initialization and inspection. v2.7.2 · Aug 2026 · 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 brutespray, 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 brutespray 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

12 entries

  1. August 20261
  2. June 20262
  3. May 20262
  4. March 20263
  5. February 20261
  6. August 20251
  7. January 20251
  8. February 20241
    Show

    12 entries

    Project health

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

    1. Contributors 2 −2 vs prior 12 months
    2. Maintainers 1 +0 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 < 1 day first maintainer reply 11 hours
    6. Open backlog 9 of 62 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 9
    3. Contributors / month 1
    4. Commits / month 1
    5. Stars 2,535
    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 →
    browse all tools → score card for your toolchain →