faraday-agent-dispatcher
3.9.1 open-sourceThe section your link pointed to isn't on faraday-agent-dispatcher's page any more, so we've brought you to the top.
Middleware dispatcher that integrates custom executors with Faraday vulnerability management platform, relaying JSON output to Faraday's Bulk Create API.
# Configuration example for TenableSCAgent # Add 'TenableSCAgent' to the agents list in your dispatcher config # Configuration example for CiscoCyberVisionAgent # Add 'CiscoCyberVisionAgent' to the agents list in your dispatcher config faraday-agent-dispatcher --executor sonarqube faraday-agent-dispatcher --executor tenableio export API_KEY_ZAP="your-zap-api-key" faraday-agent-dispatcher --zap-scan http://target faraday-agent-dispatcher run --executor nmap -sC -sV --top-ports 100 faraday-dispatcher run faraday-dispatcher wizard
Summary
faraday-agent-dispatcher is an open-source command-line agent that runs custom or vendor executors (Nmap, Tenable, Cisco Cyber Vision, Microsoft Defender, GitHub code scanning, and others) and forwards their JSON output to a Faraday server's Bulk Create API. Installed via pip as faraday-dispatcher, it is configured through a config wizard that writes an ini file, then run with a registration token pointing at your Faraday instance, which makes it a fit for teams already using Faraday to centralize vulnerability data and looking to pipe additional scanners into it rather than a standalone scanner itself. It sits in the vulnerability-management space as connective tissue between tools and a central platform. With 34 contributors, 146 commits in the past year, and a release 207 days ago, it remains actively maintained since its first commit in 2019.
Middleware dispatcher that integrates custom executors with Faraday vulnerability management platform, relaying JSON output to Faraday's Bulk Create API.
How faraday-agent-dispatcher helps
Which scanners in my stack can feed vulnerability data into a central Faraday instance without me writing a custom importer for each one?
runs the vendor executor for the tool already in use (Nmap, Tenable, Cisco Cyber Vision, Microsoft Defender, GitHub code scanning, and others) and forwards its JSON output straight to the Bulk Create API
Can I get my own scanner or internal tool's findings into Faraday alongside the rest?
accepts any script that prints single-line JSON to stdout as a valid executor, decoding and relaying each line to Faraday so a custom tool is treated the same as a vendor one
Why isn't my custom executor's output showing up in Faraday?
rejects lines that don't match the Bulk Create schema or that mix in non-JSON stdout output, so malformed or debug output printed to the wrong stream stops the send rather than silently corrupting it
Are all my scan sources reporting through the same channel, or did one integration drift onto its own path?
centralizes every configured executor's output through one dispatcher process tied to a single Faraday registration token, so a scanner outside that config simply won't appear in Faraday
Am I only pulling in the latest scan from Tenable, or every completed one?
offers a setting to retrieve all completed scans from Tenable SC instead of just the most recent, so historical scans already run aren't left out of Faraday
Will a single findings dump overwhelm the dispatcher before it reaches Faraday?
applies a configurable maximum payload size per executor, so oversized JSON from a large scan is bounded rather than failing outright
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 faraday-agent-dispatcher, 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 faraday-agent-dispatcher 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
18 entries
No entries match these filters.
- January 20261
- October 20251
- January 20251
- May 20241
- March 20241
- November 20221
- September 20221
- July 20221
- August 20212
- March 20211
- February 20211
- December 20201
- September 20201
- August 20204
Project health
Issue, contributor and maintainer activity in infobyte/faraday_agent_dispatcher, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 −1 vs prior 12 months
- Maintainers 2 +2 joined · −3 left, last 12 months
- Bus factor 1 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 12 of 23 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 12
- Contributors / month 0
- Commits / month 0
- Stars 49
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
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.