faraday-cli
2.3.0 open-sourceThe section your link pointed to isn't on faraday-cli's page any more, so we've brought you to the top.
Command-line client for Faraday that automates security workflows including managing workspaces, hosts, vulnerabilities, and tool reports.
faraday-cli auth list faraday-cli auth use bob@corp.faradaysec.com faraday-cli pentest --target https://example.com --workspace my_workspace --advanced --watch faraday-cli triage --workspace my_workspace --severities critical,high --confirmed-only --auto-close-fp --reproduce --dry-run faraday-cli pentest --target https://example.com --watch faraday-cli pentest --target https://example.com --advanced --watch faraday-cli scanners run --agent <id|name> pentest --target https://example.com --watch pentest --target https://example.com --advanced --watch scanners run --agent <id|name> faraday-cli faradai register faraday-cli faradai verify faraday-cli faradai login faraday-cli auth list faraday-cli auth use prod-server faraday-cli tool run <tool_name> --force faraday-cli host create <ip> --resolve-hostname false faraday-cli tool run --tool-name nmap --hosts <target> --create-workspace far-cli upload-evidence --vuln-id <vuln_id> --file /path/to/evidence.png far-cli workspace disable <workspace_name> faraday-cli vuln faraday-cli workspace list --show-inactive
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
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-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 → 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-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…
Releases
10 entries
No entries match these filters.
- October 20264
- September 20251
- April 20231
- December 20211
- August 20211
- June 20211
- April 20211
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.
- Contributors 2 −2 vs prior 12 months
- Maintainers 1 +1 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 4 of 15 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 4
- Contributors / month 0
- Commits / month 0
- Stars 52
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.