PAGES
← all tools
◆ Vulnerability Management

faraday-cli

2.3.0 open-source

Command-line client for Faraday that automates security workflows including managing workspaces, hosts, vulnerabilities, and tool reports.

Summary

faraday-cli is an open-source command-line client for the Faraday vulnerability-management platform, installed via pip and free to use. It lets a pentester or security team drive Faraday from the terminal instead of the web UI: authenticating, creating and selecting workspaces, listing hosts and their services, importing vulnerabilities from tool reports with severity filters, and running scans against hosts before reimporting results. It is aimed at practitioners already using Faraday to consolidate findings across engagements who want to script or automate that workflow rather than click through a browser. First committed in 2020 and maintained by 18 contributors, it has had 14 commits in the past year and a release 99 days ago, putting it on a slow but active cadence.

Command-line client for Faraday that automates security workflows including managing workspaces, hosts, vulnerabilities, and tool reports.

How faraday-cli helps

Which hosts turned up in this engagement, and what is running on each one?

lists every host in the active workspace with its OS, hostname, service count, and vulnerability count, pulled straight from Faraday's stored data

Which of these findings actually matter enough to act on first?

imports a tool report filtered to a minimum and maximum severity, so only vulnerabilities in that range land in the workspace instead of the whole unfiltered dump

Do I already have a scan of this host, or do I need a fresh one?

runs a scan against a host directly from the terminal and reimports the results, replacing manual export-then-upload steps with one command

How much has this engagement grown since I last checked?

lists every workspace with its current host, service, and vulnerability counts side by side, so growth or gaps show up without opening each one

Has someone already logged this vulnerability under another name?

pulls up the stored details for a specific host, showing its existing vulnerabilities so duplicates are visible before a new report gets imported

all 13 features, with the evidence for each →

Languages

Not documented

Features

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

Built from faraday-cli'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 →

  • faraday-cli covers 1 of the 13 network discovery and scanning capabilities we track.

What faraday-cli offers you

  • Command-line interface7
All capabilities 13 capabilities
Paginated results navigation verified Controls pagination of list output via page selection, result limits, and optional non-interactive mode. 1 release · 6 other sources · first seen Apr 2021

release

  • Adds a new vuln subcommand to list vulnerabilities directly from the CLI. v1.1.0 · Apr 2021 · source · release history

command line

example

  • List all vulnerabilities in the current workspace without leaving the terminal. faraday-cli vuln v1.1.0 · Apr 2021 · source
  • Get details for a specific host faraday-cli host get 574
  • List all hosts in active workspace faraday-cli host list
FaradAI cloud scanner management verified suggested Lists, inspects, and runs FaradAI cloud agents (scanners) and launches AI-driven pentest and triage workflows against a target from the CLI. 2 releases · 4 other sources · first seen Oct 2026

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Adds faraday-cli scanners with list, get, and run subcommands to manage FaradAI cloud agents from the CLI.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 2.3.0 · Oct 2026 · source · release history
  • Adds faraday-cli faradai scan and faraday-cli faradai triage shortcuts (with pentest/triage modes) to launch FaradAI cloud scans and triage workflows. 2.3.0 · Oct 2026 · source · release history

docs

  • AI pentest with FaradAI Launch an AI-driven pentest against a target using the FaradAI cloud agent (scanner) and watch it to completion. pentest --target https://example.com --watch !!! info pentest is the shortcut for faradai scan . docs update · Oct 2026 · source

command line

  • scanner_id — ID of the cloud agent 2.3.0 · Oct 2026 · command-line history
  • agent_pos — Cloud-agent id or name/slug (e.g. first-scan). Same as -a. 2.3.0 · Oct 2026 · command-line history
  • --wizard — Force the interactive parameter wizard even if --param was given 2.3.0 · Oct 2026 · command-line history
Workspace filtering verified Filters results by specifying one or more workspace names. 2 releases · 4 other sources · first seen Apr 2021

Also counts toward: Command-line interface

release

  • Adds --force flag to tool run to process command output regardless of the return code. 2.1.10 · Apr 2023 · source · release history
  • Adds a new --show-inactive flag to the workspace listing commands to include inactive workspaces in results. v1.1.0 · Apr 2021 · source · release history

command line

  • --workspace — Workspace name to triage (repeatable, at least one required) 2.3.0 · Oct 2026 · command-line history
  • --workspaces-names — Workspace name 2.1.12 · Jan 2025 · command-line history

example

  • Force process tool output even if the underlying command returns a non-zero exit code. faraday-cli tool run <tool_name> --force 2.1.10 · Apr 2023 · source
  • View all workspaces including those that have been archived or closed. faraday-cli workspace list --show-inactive v1.1.0 · Apr 2021 · source
Vulnerability severity filtering on import verified Limits which vulnerabilities are imported by specifying a minimum and maximum severity threshold. 1 release · 4 other sources · first seen Sep 2025

release

  • Adds --min-severity and --max-severity parameters to filter vulnerabilities by severity range during import. 2.2.0 · Sep 2025 · source · release history

command line

  • --max-severity — Maximum severity of vulnerabilities to import 2.2.0 · Sep 2025 · command-line history
  • --min-severity — Minimum severity of vulnerabilities to import 2.2.0 · Sep 2025 · command-line history

example

  • Import vulnerabilities from tool report faraday-cli tool report "/path/to/report.xml"
  • Scan hosts on port 443 and import results faraday-cli host list --port 443 -ip | nmap -iL - -oX /tmp/nmap.xml && faraday-cli process_report /tmp/nmap.xml
Named connection session management verified Saves, lists, switches between, and removes named connection sessions so the CLI can work across multiple Faraday environments without re-authenticating each time. 1 release · 3 other sources · first seen Oct 2026

Also counts toward: Command-line interface

release

  • Adds faraday-cli auth list, auth use, and auth rm to manage named connection sessions for multiple Faraday environments. 2.3.0 · Oct 2026 · source · release history

docs

  • -n/--name NAME Session name to save this connection as (default: the server host) One active connection, multiple saved sessions faraday-cli keeps one active connection at a time, but remembers the others as named sessions so you can switch instead of being logged in to two servers at once. docs update · Oct 2026 · source

command line

  • session — Session to remove — the ID number, name, or user from 'auth list' 2.3.0 · Oct 2026 · command-line history

example

  • Switch between named Faraday connection sessions when working across multiple environments. faraday-cli auth list faraday-cli auth use prod-server 2.3.0 · Oct 2026 · source
Workspace management shipped Provides commands to deactivate workspaces and automatically create new ones during scanning. 1 release · 3 other sources · first seen Jun 2021

Also counts toward: Command-line interface

release

  • Adds --create-workspace parameter to the tool command to automatically create workspaces if they do not exist v2.0.2 · Aug 2021 · source · release history

example

  • Run a tool scan in a new workspace without pre-creating it manually via the UI or API. faraday-cli tool run --tool-name nmap --hosts <target> --create-workspace v2.0.2 · Aug 2021 · source
  • Deactivate a workspace to stop scanning activity far-cli workspace disable <workspace_name> 2.0.0 · Jun 2021 · source
  • Create a new workspace faraday-cli workspace create some_name
FaradAI SaaS account registration and login verified Creates and verifies a new FaradAI SaaS account and authenticates to it entirely from the CLI, without requiring a self-hosted Faraday server. 1 release · 2 other sources · first seen Oct 2026

Also counts toward: Command-line interface

release

  • Adds faraday-cli faradai register, faradai verify, and faradai login for SaaS onboarding — sign up and scan without a self-hosted Faraday server. 2.3.0 · Oct 2026 · source · release history

command line

  • code — 6-digit verification code (positional; or use --code) 2.3.0 · Oct 2026 · command-line history

example

  • Register and verify a new FaradAI SaaS account entirely from the CLI to start scanning immediately. faraday-cli faradai register faraday-cli faradai verify faraday-cli faradai login 2.3.0 · Oct 2026 · source
Hostname configuration control shipped Allows creating host entries without automatic hostname resolution and provides options to explicitly control whether hostnames are resolved. 2 releases · 1 other source · first seen Apr 2023

Also counts toward: Command-line interface

release

  • The default value for hostname resolution is now false (previously true), so host create will no longer resolve hostnames by default. 2.1.10 · Apr 2023 · source · release history
  • Adds --resolve-hostname flag to the host create subcommand to control hostname resolution. 2.1.10 · Apr 2023 · source · release history

example

  • Create a host entry without resolving its hostname. faraday-cli host create <ip> --resolve-hostname false 2.1.10 · Apr 2023 · source
Evidence attachment shipped Enables attaching proof files or other evidence to specific vulnerability records. 1 release · 1 other source · first seen Jun 2021

Also counts toward: Command-line interface

release

  • upload-evidence command added to attach files to specific vulnerabilities 2.0.0 · Jun 2021 · source · release history

example

  • Attach a proof file to a vulnerability record far-cli upload-evidence --vuln-id <vuln_id> --file /path/to/evidence.png 2.0.0 · Jun 2021 · source
Host discovery and details shipped Enables listing all hosts in the active workspace and retrieving specific details for individual hosts. 2 other sources

Shared capability: Attack surface inventory

example

  • Get details for a specific host faraday-cli host get 574
  • List all hosts in active workspace faraday-cli host list
Vulnerability tagging shipped Allows associating custom tags with vulnerabilities for categorization and filtering. 1 release · first seen Apr 2021

release

  • Adds support for tagging vulnerabilities via the new tags feature. v1.1.0 · Apr 2021 · source · release history
Authentication configuration shipped Allows configuring authentication credentials for the Faraday CLI client. 1 other source

example

  • Configure authentication for faraday-cli faraday-cli auth
Workspace creation and management shipped Provides commands to create new workspaces, deactivate existing ones, and manage the workspace environment. 1 other source

example

  • Create a new workspace faraday-cli workspace create some_name

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-cli, 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-cli 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

10 entries

  1. October 20264
  2. September 20251
  3. April 20231
  4. December 20211
  5. August 20211
  6. June 20211
  7. April 20211
    Show

    10 entries

    Project health

    Issue, contributor and maintainer activity in infobyte/faraday-cli, 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 +1 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 4 of 15 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 4
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 52
    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

    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 →