Repository navigation
WebFang v7.7.0
What's Changed
See CHANGELOG for details.
Installation
WebFang ships binaries only — nothing is published to crates.io, so cargo install webfang does not work. Download the archive for your platform from the assets below.
| Platform | Asset |
|---|---|
| Linux x86_64 | webfang-x86_64-unknown-linux-gnu.tar.gz |
| Linux ARM64 | webfang-aarch64-unknown-linux-gnu.tar.gz |
| macOS Apple Silicon | webfang-aarch64-apple-darwin.tar.gz |
| Windows x86_64 | webfang-x86_64-pc-windows-msvc.zip |
Each platform also ships the MCP servers, one binary per archive: webfang-mcp-<target> (Streamable HTTP) and webfang-mcp-stdio-<target> (stdio, for desktop clients that spawn the server). Both expose the same 36 tools. Install notes: https://github.com/XaviCodeDev1000/webfang/blob/main/docs/src/installation.md#mcp-servers-from-the-release-artifact
There is no Intel macOS artifact — the published targets are Linux x86_64, Linux ARM64, macOS Apple Silicon and Windows x86_64; Intel macOS is not in the list. Build from source (see the From source section below) if you need an Intel Mac build.
Every archive holds exactly ONE bare binary (webfang.exe, webfang-mcp.exe or webfang-mcp-stdio.exe on Windows). Nothing installs it for you — extract it, make it executable, and put it on your PATH:
# Linux / macOS
tar xzf webfang-<target-triple>.tar.gz
sudo install -m 0755 webfang /usr/local/bin/webfang # or, no sudo: install -m 0755 webfang ~/.local/bin/webfang
webfang --version# Windows
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\bin" | Out-Null
Move-Item -Force webfang.exe "$env:USERPROFILE\bin\webfang.exe"
webfang --versionPlatform requirements: glibc 2.39 or newer on Linux (the artifacts link glibc directly and there is no musl build), the Microsoft Visual C++ Redistributable 2015-2022 (x64) on Windows (MSVC's default dynamic CRT), and on macOS the com.apple.quarantine flag must be cleared with xattr -d com.apple.quarantine webfang if Gatekeeper kills the first run.
From source
Requires Rust 1.91, a C/C++ compiler, and cmake. The HTTP client wreq → btls → btls-sys (formerly boring2/boring-sys2) compiles BoringSSL from C++ on first build, and without cmake the failure surfaces deep inside a build script with an error that never mentions the real cause.
git clone https://github.com/XaviCodeDev1000/webfang
cd webfang
cargo build --release --locked --features "webfang_cli/mcp" -p webfang_cli -p webfang_mcp --binsVerification
Verify the checksum of the archive you downloaded before extracting it. SHA256SUMS.txt lists all twelve archives. The command differs per platform: sha256sum is GNU coreutils and exists on neither stock macOS nor PowerShell.
# Linux
sha256sum -c SHA256SUMS.txt --ignore-missing
# macOS
shasum -a 256 webfang-aarch64-apple-darwin.tar.gz
grep aarch64-apple-darwin SHA256SUMS.txt# Windows
(Get-FileHash webfang-x86_64-pc-windows-msvc.zip -Algorithm SHA256).Hash.ToLower()
Select-String -Path SHA256SUMS.txt -Pattern pc-windows-msvcFull install and uninstall guide, including every on-disk root a run leaves behind: https://github.com/XaviCodeDev1000/webfang/blob/main/docs/src/installation.md
Provenance Attestation (L1)
| Property | Value |
|---|---|
| Tag | v7.7.0 |
| Validated Commit | 2d4656ceb580f2d4347cd590d39a5ab173e022cd |
| Lineage | main (ancestor) |
| Channel | Stable |
| L1 Gate | `check_release_provenance.sh preflight |
| Ruleset | release-tags-immutable (update + deletion blocked) |
| Signed Ref | refs/tags/v7.7.0 (trigger: push) |
Signature Verification (keyless)
Every archive, SHA256SUMS.txt and the SBOM carries a sibling .sigstore.json bundle, signed with cosign in keyless mode. The certificate identity is this repository's release workflow, and the ref this release was signed at is the Signed Ref above — both are pinned, so a bundle produced by any other run is rejected.
cosign verify-blob --bundle webfang-x86_64-unknown-linux-gnu.tar.gz.sigstore.json --certificate-identity-regexp '^https://github\.com/XaviCodeDev1000/webfang/\.github/workflows/release\.yml@refs/(heads|tags)/.+$' --certificate-oidc-issuer https://token.actions.githubusercontent.com --certificate-github-workflow-ref refs/tags/v7.7.0 --certificate-github-workflow-trigger push webfang-x86_64-unknown-linux-gnu.tar.gzscripts/verify-release-signatures.sh on main runs exactly this over every published asset and prints the identity it used. Use the script from main: the copy at an older tag predates the claim pinning and rejects these flags (webfang#2479).