[Name] crossfyre-toolchain (Crossfyre Toolchain)
[Version] 0.1.42
[Homepage] https://crossfyre.io/toolchain
[Download] Source at the tag: https://github.com/clickswave/crossfyre-toolchain/tree/v0.1.42
Release tarballs for amd64 and arm64, built from the tag and attested by GitHub Actions,
with SHA256SUMS: https://github.com/clickswave/crossfyre-toolchain/releases/tag/v0.1.42
(gh attestation verify <file> --repo clickswave/crossfyre-toolchain checks one).
[Author] Clickswave Labs Pvt Ltd, https://clickswave.org. I work on it there.
[Licence] Apache License 2.0, every crate in the repository (LICENSE at its root).
Third-party crates are under their own permissive licences, listed in Cargo.lock.
[Description] Five scanning engines and the CLI that runs them, for systems you are
authorized to test. voyage finds subdomains, from passive sources and wordlists.
doorward scans hosts and ports with service detection. ambulo does content discovery.
toolmark fingerprints services and technologies and flags CVE leads by version. plessor
tests for vulnerabilities with nuclei-compatible templates and confirms each finding
before it reports it, including blind ones through its own out-of-band server, oast.
The engines share one output format (newline-delimited JSON), one terminal dashboard
and one CLI, crossfyre, and a stopped scan resumes where it left off. Everything works
on its own, with no account; a node agent can connect the engines to a hosted
platform, and nothing leaves the machine unless the user does that.
[Dependencies] glibc 2.34 or later. cfx-script, which runs .cfx scripts, needs Python
3.10 or later (libpython3). The prebuilt tarball carries its own CPython 3.13 in
python/, with its notices in THIRD-PARTY-NOTICES-PYTHON.txt; a Kali package would
rather build cfx-script from source against the system Python and leave that
directory out. Recommended: docker.io, since the engines keep scan state in a local
Postgres that crossfyre db up runs as a container.
[Similar tools] subfinder, amass, nmap, ffuf, httpx, nuclei
[Activity] Public on GitHub since September 2026, with CI on Linux, macOS and Windows.
Seven releases from v0.1.36 (2026-10-26, which added macOS and Windows) to v0.1.42
(2026-11-11), and pull requests from outside contributors merged in that time.
Developed by Clickswave Labs.
[How to install] cargo build --release --locked at the tag builds every binary, with
the Rust 1.88.0 toolchain that rust-toolchain.toml pins. Or from the release tarball,
which holds crossfyre, node, voyage, doorward, ambulo, toolmark, plessor, oast and
cfx-script.
Suggested layout: /usr/bin/crossfyre, the other binaries in /usr/lib/crossfyre/bin/,
and /usr/lib/crossfyre/packaging.json:
{
"manager": "apt",
"owns": ["crossfyre", "node", "cfx-script", "ambulo", "voyage", "doorward", "toolmark", "plessor"],
"bin_dir": "/usr/lib/crossfyre/bin"
}
With that file the CLI leaves every component to apt: crossfyre update and crossfyre
extension install never download or replace a packaged binary, and crossfyre doctor
reports the install as apt's. Tested on 2026-11-16 in the kalilinux/kali-rolling
image, amd64, with the v0.1.42 tarball laid out that way: all nine binaries start and
print their version, and crossfyre doctor reports "installed by apt" with the bin_dir
above. The same layout was tested on Parrot, where crossfyre update all reports each
component as installed by apt and downloads nothing.
[How to use]
voyage scan --domain example.com --wordlist-path ./subdomains.txt
doorward scan --targets 10.0.0.0/24 --ports top-1000 --service-detection
ambulo scan --url https://example.com/::FUZZ:: --wordlist-path ./wordlist.txt
Each prints a dashboard in a terminal and newline-delimited JSON when piped, and
exits non-zero if the run ends in an error. --help on any command for the rest.
[Packaged] Not in Debian. Upstream publishes its own build in an apt repository
(https://crossfyre.io/docs/install) as a package named crossfyre, which also installs
/usr/bin/crossfyre, so this package should conflict with that one. |