rekono-kbx
2.0.0-1 open-sourceThe section your link pointed to isn't on rekono-kbx's page any more, so we've brought you to the top.
Offensive security platform that automates attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. discovery and vulnerability management
curl -s -H 'Authorization: Bearer <token>' https://<rekono-host>/api/settings/ curl -s -H 'Authorization: Bearer <token>' https://<rekono-host>/api/settings/ POST /api/v1/targets with an array of target objects POST /api/v1/tasks with a list of target IDs in the 'targets' field
Summary
rekono-kbx is an open-source platform that orchestrates existing pentesting tools like Nuclei, Gobuster, and Spring4Shell Scan into automated workflows across one or more targets, consolidating recon and scanning into a single task pipeline. It runs as a self-hosted web application with background workers, and can also be installed as a standalone desktop app on Linux, MacOS, and Windows for users who prefer a local client over a server deployment. It is built for pentesters and red teamers who otherwise juggle separate recon tools by hand, covering triage of findings as true positive, false positive, or won't-fix, report generation in PDF, JSON, or XML, and enrichment via VirusTotal, HackTricks, and CVE Crowd. First committed in 2021, it has 7 contributors and remains active, with 179 commits and 4 releases in the past year, the latest 42 days ago.
Offensive security platform that automates attack surface discovery and vulnerability management
How rekono-kbx helps
Which hosts and services on a target scope have exploitable findings worth chasing?
chains recon and scanning tools end to end against the defined targets and consolidates what each tool reports into a single finding set, correlating hosts, ports and vulnerabilities as the chain runs
Has anything changed since the last time a target was assessed?
tracks each finding's exposure window across executions and marks a finding fixed automatically once later runs stop reporting it, so re-running a target shows what's new, persistent or resolved
Are any of the CVEs turning up on this engagement actually being talked about right now?
cross-checks detected CVEs against CVE Crowd and flags the ones trending on social media, alongside CVSS and NVD enrichment pulled in for each finding
Which findings still need a decision before they go in the report?
lets a practitioner triage every finding as true positive, false positive or won't fix with a comment, and only the triaged set feeds into generated reports
How do I get a client-ready report out of a completed engagement without writing it by hand?
generates PDF, JSON or XML output filtered by the criteria chosen, using a customisable HTML template for the PDF form
Who needs to know the moment a specific kind of finding shows up during a long-running engagement?
matches new findings against saved alert criteria and pushes a notification to that alert's subscribers as soon as a match is discovered
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 rekono-kbx, 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 rekono-kbx 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
10 entries
No entries match these filters.
- August 20262
- May 20231
- March 20231
- January 20231
- November 20222
- October 20221
- September 20221
- August 20221
Project health
Issue, contributor and maintainer activity in pablosnt/rekono, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 ±0 vs prior 12 months
- Maintainers 2 +2 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 14% of issues opened, last 12 months
- Median time to close 2.2 days first maintainer reply 12 hours
- Open backlog 1 of 115 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 1
- Commits / month 3
- Stars 608
- bugs 14%
- features 36%
- other 50%
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.