PAGES
← all tools
◆ Vulnerability Management

faraday-agent-dispatcher

3.9.1 open-source

Middleware dispatcher that integrates custom executors with Faraday vulnerability management platform, relaying JSON output to Faraday's Bulk Create API.

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

all 6 features, with the evidence for each →

Languages

Not documented

Features

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

Built from faraday-agent-dispatcher'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 faraday-agent-dispatcher offers you

  • Command-line interface1
All capabilities 6 capabilities
Executor management and configuration shipped Allows users to configure execution parameters, handle environment variables, manage executor dependencies, and adjust operational constraints such as timeouts and hostname resolution for various security agents. 17 releases · 3 other sources · first seen Aug 2020

release 17 total

  • Refactors executor parameters to eliminate code duplication 3.9.0 · Oct 2025 · source · release history
  • Adds sonarqube executor for scanning projects with SonarQube 2.5.0 · Nov 2022 · source · release history
  • Adds tenableio executor for scanning assets with Tenable.io 2.5.0 · Nov 2022 · source · release history
  • Remove ws from dispatcher.yaml. 2.2.0 · Jul 2022 · source · release history
  • Now faraday-dispatcher send the parameters of the executors when it connects to faraday server. Also it checks if there are new enviroment variables defined in the manifest file and warn the user. 2.2.0 · Jul 2022 · source · release history
  • Adds timeout parameter to arachni's executor 2.2.0 · Jul 2022 · source · release history

example

  • Execute a SonarQube scan using the new executor. faraday-agent-dispatcher --executor sonarqube 2.5.0 · Nov 2022 · source
  • Execute a Tenable.io scan using the new executor. faraday-agent-dispatcher --executor tenableio 2.5.0 · Nov 2022 · source
  • Pass custom nmap arguments directly from the command line for granular scanning control. faraday-agent-dispatcher run --executor nmap -sC -sV --top-ports 100 1.4.0 · Dec 2020 · source
CLI configuration verified Allows users to configure the tool via a config file, log level, debug mode, pagination size, and registration token through command-line options. 5 releases · 8 other sources · first seen Jun 2020

Also counts toward: Command-line interface

release

  • Nikto now uses only requieres TARGET_URL argument. 2.2.0 · Jul 2022 · source · release history
  • Adds --page-size argument to faraday-dispatcher config-wizard --help for customizing wizard page size 1.3.0 · Sep 2020 · source · release history
  • The run command includes automatic configuration migration logic similar to the config-wizard 1.3.0 · Sep 2020 · source · release history
  • Adds faraday-dispatcher wizard subcommand to generate a configuration .ini file 1.1 · Aug 2020 · source · release history
  • Adds dispatcher.ini configuration file to define fixed parameters such as passwords that should not come from the web 1.0 · Aug 2020 · source · release history

docs

  • Middleware dispatcher that integrates custom executors with Faraday vulnerability management platform, relaying JSON output to Faraday's Bulk Create API.

command line

example

  • Generate a default configuration file for first-time setup. faraday-dispatcher wizard 1.1 · Aug 2020 · source
  • Run configuration wizard for dispatcher faraday-dispatcher config-wizard
Agent integration and data ingestion shipped Provides agents to ingest findings and scan results from various external platforms and scanners including ZAP, SonarQube, GitHub, Tenable SC, Cisco Cyber Vision, and Nessus. 7 releases · 2 other sources · first seen Aug 2021

release 7 total

  • New option to retrieve all completed scans from Tenable SC, not just the latest. 3.6.0 · Jan 2025 · source · release history
  • Adds TenableSCAgent to import Tenable Security Center scan results 3.4.0 · May 2024 · source · release history
  • Adds CiscoCyberVisionAgent to ingest Cisco Cyber Vision data 3.4.0 · May 2024 · source · release history
  • Adds hotspot detection capability for SonarQube integrations 3.3.0 · Mar 2024 · source · release history
  • Adds github_codeql agent integration for SAST scanning via GitHub's CodeQL engine 3.3.0 · Mar 2024 · source · release history
  • API_KEY_ZAP (env var) now controls the ZAP API authentication instead of inline config or prompt. 2.3.0 · Sep 2022 · source · release history

example

  • Ingest Cisco Cyber Vision data by enabling the new agent in the dispatcher setup. # Configuration example for CiscoCyberVisionAgent # Add 'CiscoCyberVisionAgent' to the agents list in your dispatcher config 3.4.0 · May 2024 · source
  • Ingest Tenable SC scan results by configuring the new agent in the dispatcher setup. # Configuration example for TenableSCAgent # Add 'TenableSCAgent' to the agents list in your dispatcher config 3.4.0 · May 2024 · source
Dispatch operation and scaling shipped Supports starting the dispatcher with specific configurations, handles larger payloads through increased default limits, and lists available templates for scanners. 4 releases · 3 other sources · first seen Aug 2020

release

  • Increases the default max_size value, enabling agents to handle larger payloads without manual configuration. 3.9.1 · Jan 2026 · source · release history
  • Adds duration support to the bulk_create method for correct timing control 1.4.0 · Dec 2020 · source · release history
  • The run command includes automatic configuration migration logic similar to the config-wizard 1.3.0 · Sep 2020 · source · release history
  • Introduces the faraday-dispatcher run subcommand to execute the dispatcher 1.1 · Aug 2020 · source · release history

example

  • Start the dispatcher service using the new CLI entry point. faraday-dispatcher run 1.1 · Aug 2020 · source
  • Start the Faraday agent dispatcher faraday-dispatcher run
  • Run dispatcher with a specific config file faraday-dispatcher --config-file PATH_TO_A_CONFIG_FILE
Authentication and environment handling shipped Manages authentication for external APIs via environment variables instead of inline config, and handles dynamic environment variable discovery from manifests. 4 releases · 1 other source · first seen Aug 2021

release

  • The burp agent's TARGET_URL parameter type is changed from a single URL string to a list of URLs. #229 3.9.0 · Oct 2025 · source · release history
  • Updates TARGET_URL parameter in the burp agent to accept a list of URLs 3.9.0 · Oct 2025 · source · release history
  • API_KEY_ZAP (env var) now controls the ZAP API authentication instead of inline config or prompt. 2.3.0 · Sep 2022 · source · release history
  • Adds ssl_verify (or equivalent) configuration key in the YAML file to allow ignoring SSL certificate verification errors 2.1.1 · Aug 2021 · source · release history

example

  • Pass ZAP API key via environment variable for automated runs. export API_KEY_ZAP="your-zap-api-key" faraday-agent-dispatcher --zap-scan http://target 2.3.0 · Sep 2022 · source
Multi-workspace data posting shipped Allows agents to post scan results and findings to multiple workspaces simultaneously. 1 release · first seen Sep 2020

release

  • Agents can now post data to multiple workspaces simultaneously 1.3.0 · Sep 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 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 →

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…

Explore the full chart →

Releases

Show

18 entries

  1. January 20261
  2. October 20251
  3. January 20251
  4. May 20241
  5. March 20241
  6. November 20221
  7. September 20221
  8. July 20221
  9. August 20212
  10. March 20211
  11. February 20211
  12. December 20201
  13. September 20201
  14. August 20204
    Show

    18 entries

    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.

    1. Contributors 5 −1 vs prior 12 months
    2. Maintainers 2 +2 joined · −3 left, last 12 months
    3. Bus factor 1 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 12 of 23 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 12
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 49
    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

    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 →