Faraday Vulnerability Manager
Aggregate and normalize scanner and pentest results so teams track and remediate vulnerabilities in one shared workspace.
- Source repo
- infobyte/faraday
- Stars
- ★ 6.9k
- Last updated
- 22d ago
- License
- GPL-3.0
- Primary language
- Python
- FA score
- 46/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free tier plus a paid hosted plan
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- Pentest teams where several operators scan in parallel and need all findings merged into one shared workspace instead of merging spreadsheets by hand.
- Not a fit if
- Solo users who want a single scanner, not a server plus database
- Environments that require a zero-dependency offline single binary
- Teams that only need one-off scan output and no shared aggregation
- Website
- faradaysec.com ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-10-29latest release v5.25.4 (2026-10-29)+2.3 ★/day over 7 days
- Source review
- 46/100 · Major gaps 1 safety controls not found
What does this agent do, and when should you use it?
Faraday is an open-source vulnerability management platform from Infobyte, licensed GPL-3.0 and built in Latin America but used worldwide. It aggregates and normalizes output from security tools, organizes findings into a truly multiuser workspace, and exposes them through dashboards and visualizations aimed at both managers and analysts. The product consists of a server (faraday-server), a database bootstrap command (faraday-manage initdb), a web UI on port 5985, and the faraday-cli terminal client. Teams can either run scanners directly, or import previously generated artifacts, and can drive scanners remotely through the separate Faraday Agents Dispatcher. Over 80 tools are supported via plugins.
Faraday reads, aggregates and normalizes security tool output through two plugin types. Console plugins interpret the output of tools you execute, for example faraday-cli tool run "nmap www.exampledomain.com" parses the Nmap run and sends the data to a named workspace. Report plugins import previously generated artifacts such as XML or JSON, for example faraday-cli tool report burp.xml. The README states more than 80 supported tools, with the full list in the Plugin-List wiki page. Collected findings land in a multiuser workspace and can be explored through different visualizations in the web UI; faraday-cli can also fetch workspace metrics for automation. The server is bootstrapped with faraday-manage initdb and started with faraday-server, listening on 5985, where the default login is user faraday with the password produced by the installation. Remote scanner execution is provided by the Faraday Agents Dispatcher, and the API is documented separately.
- Pentest teams where several operators scan in parallel and need all findings merged into one shared workspace instead of merging spreadsheets by hand.
- DevSecOps engineers wiring Bandit, OWASP ZAP or SonarQube into GitHub, Jenkins, TravisCI or GitLab pipelines and routing results into a single tracker.
- Security managers who need dashboards and vulnerability metrics rather than raw scanner output.
- Analysts who already have a Burp XML report and want to import and explore it visually instead of reading raw text.
- Automation engineers using faraday-cli from terminal scripts or CI jobs to pull workspace metrics and trigger work.
- Teams that need remote execution: Faraday Agents Dispatcher lets the platform run scanners or tools remotely and collect the results.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Install / run
docker run \pip3 install faradaysecpip3 install virtualenvpip3 install
- Environment variables
PGSQL_HOST- Install notes cover
- Linux · Docker
How do you install or deploy this agent?
The easiest path is the official docker-compose example: download and bring it up.
wget https://raw.githubusercontent.com/infobyte/faraday/master/docker-compose.yaml
docker-compose upRunning the Docker image directly requires a PostgreSQL instance to be available first.
docker run \
-v $HOME/.faraday:/home/faraday/.faraday \
-p 5985:5985 \
-e PGSQL_USER='postgres_user' \
-e PGSQL_HOST='postgres_ip' \
-e PGSQL_PASSWD='postgres_password' \
-e PGSQL_DBNAME='postgres_db_name' \
faradaysec/faraday:latestPyPi install:
pip3 install faradaysec
faraday-manage initdb
faraday-serverBinary packages (Debian/RPM) are on the releases page:
sudo apt install faraday-server_amd64.deb
faraday-manage initdb
sudo systemctl start faraday-serverFrom source:
pip3 install virtualenv
virtualenv faraday_venv
source faraday_venv/bin/activate
git clone [email protected]:infobyte/faraday.git
pip3 install .
faraday-manage initdb
faraday-serverAfter installation, add your user to the faraday group. The README defers detailed, platform-specific instructions to the installation wiki.
How do you use this agent?
Start the server, then open the web UI and log in as faraday with the password produced during installation:
http://localhost:5985Install the CLI client:
pip3 install faraday-cliRun a tool through Faraday and push results into a workspace:
faraday-cli tool run "nmap www.exampledomain.com"Import a report you already have:
faraday-cli tool report burp.xmlWhat are this agent's strengths and limitations?
- Normalizes findings from many tools into one multiuser workspace, which is the collaboration model single-machine scanners lack.
- Two plugin paths — Console for live tool runs and Report for existing XML/JSON artifacts — cover both active and retrospective workflows.
- Multiple documented deployment paths: docker-compose, Docker, PyPi, Debian/RPM packages and source installs.
- Ships a dedicated CLI (faraday-cli) plus published API and CLI documentation, making CI/CD and automation integration straightforward.
- Faraday Agents Dispatcher adds remote scanner execution driven from the platform.
- Requires standing up a server plus PostgreSQL; initdb, database env vars and service management go well beyond a single-binary tool.
- The README pushes install detail out to external wikis and docs sites, so a fully self-contained configuration reference is not in the repo.
- The Docker route depends on an external PostgreSQL you must supply, along with its credentials and database name.
- Although the repository description mentions AI and autonomous pentesting topics, the README details only aggregation, plugins, CLI and the Agents Dispatcher, so those AI capabilities are not verifiable from this source.
- The workflow and UI are oriented to teams; solo, one-off scanning is heavyweight for this design.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Faraday Vulnerability Manager This agent | 46 · Major gaps | Self-hosted serviceFreemium | ★ 6.9k | 22d ago | Python | — |
| DarkMoon Autonomous Pentesting | 50 · Major gaps | CLIFree + model costs | ★ 1.3k | today | Python | OpenAI API · Claude API |
| Strix AI Pentesting | 69 · Some gaps | CLIFreemium | ★ 77k | 1d ago | Python | ChatGPT · Codex · Claude Code · OpenAI API · Claude API |
| PentestCode | 45 · Major gaps | CLIFree + model costs | ★ 1.2k | 16d ago | TypeScript | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The application source shows login/security components, agent authentication routes, an audit logger, and a password complexity rule, so basic access controls are present; however, the supplied source is truncated at route registration and cannot establish the authorization boundaries of individual features. The README describes remote scanner execution, report import, and CI/CD integration without showing per-action confirmation, least-privilege controls, detailed data flows, or recovery mechanisms, so those scores remain low. The security guide recognizes the sensitivity of stored data and recommends SSL, but does not explain at-rest protection or key management. The dependency lists contain many direct dependencies, and requirements.txt disagrees with pyproject.toml on the faraday-plugins lower bound; no audit or mitigation evidence is supplied. Source headers and a vulnerability reporting channel are clear, supporting a higher attribution score.
The README, source, packaging metadata, and tests consistently indicate a server-side vulnerability management platform, but the README's login description is vague and dependency requirements differ between files. The docs provide Docker, PyPI, system package, and source installation paths, but the sample does not establish dependency availability, a compatibility matrix, or broad troubleshooting coverage. Sample tests show asynchronous tasks skipped when Celery configuration is unavailable, and user-facing failure guidance is not supplied, so these criteria receive partial scores.
The README identifies managers and analysts and describes multi-user vulnerability aggregation, plugins, CLI, agents, and CI/CD scenarios. Installation paths cover containers, packages, and source for several deployment styles. Capability boundaries are mostly described at a high level; trust boundaries and precise triggering conditions for scanner execution, agents, and the platform are not clear, so those criteria receive partial scores.
The README organizes installation, getting started, CLI, agents, plugins, API, and links, with setup commands, usage examples, and an FAQ link. Both LICENSE and project metadata specify GPL-3.0. The README points to release notes, but their contents are not included in the sample; maintenance responsibility is partly visible through the development team, security contact, and issue tracker. Known limitations and a supported-environment matrix are sparse, so those criteria do not receive full marks.
The README describes aggregating and normalizing scanner results, visualizations for different roles, and gives Nmap and report-import examples that clarify intended outputs. Cross-tool, multi-user management and CI/CD integration indicate practical value beyond using scanners independently. However, operating costs, resource needs, and maintenance burden are not quantified, and deployment security guidance is brief.
README claims about installation, CLI, plugins, and agents have concrete commands or examples. Project metadata, the license file, and source headers corroborate some licensing and attribution information. Many product benefits and compatibility claims remain summaries, and the README, dependency lists, and sample tests do not independently corroborate the full feature set or deployment reliability.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- This is a privileged server-side platform for security testing and vulnerability management; before deployment, review which commands agents can run, their user and workspace permissions, and authorized target scope.
- The platform stores highly sensitive vulnerability data and includes credential fields; the supplied material recommends SSL in transit but does not describe at-rest protection or key management.
- requirements.txt and pyproject.toml specify different minimum versions for faraday-plugins; the sample does not establish the impact.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
* [MOD] Added Markdown support on the description of the What's New items. #3152View on GitHub ↗ -
Release notes excerpt
* [MOD] Improved performance of the workspaces list and other API endpoints by reducing database queries. #8595View on GitHub ↗ -
Release notes excerpt
* [FIX] Reduced database connection usage so shared databases do not run out of connections: the connection pool is now configurable in server.ini with a lower default, Celery beat and workers close the connections they kept open from startup, faraday-worker without --concurrency now starts at most celery_max_worker_concurrency processes (default 2, previously one per CPU core), and each process is identified by application_name in PostgreSQL. #8547View on GitHub ↗
FAQ
Is Faraday free to use?
What infrastructure does it require?
Can I import reports I already generated?
faraday-cli tool report burp.xml. The README claims support for more than 80 tools, listed on the Plugin-List page.Can it run inside a CI/CD pipeline?
How does remote scanner execution work?
Is Faraday Vulnerability Manager open source?
Is Faraday Vulnerability Manager safe to use?
Is Faraday Vulnerability Manager still maintained?
Who makes Faraday Vulnerability Manager?
What is Faraday Vulnerability Manager's official website?
Thanks — we use this to improve the page.