Installation
flareover ships as a single, statically-linked binary with zero external runtime dependencies. Pick whichever install path fits your platform.
Homebrew (macOS / Linux)
Section titled “Homebrew (macOS / Linux)”brew install fabriziosalmi/flareover/flareoverVerified install script (Linux / macOS)
Section titled “Verified install script (Linux / macOS)”Downloads the release for your OS/arch and checks its sha256 before installing:
curl -fsSL https://raw.githubusercontent.com/fabriziosalmi/flareover/main/install.sh | shFrom source
Section titled “From source”go install github.com/fabriziosalmi/flareover/cmd/flareover@latestBuilding from source requires Go 1.25+. The engine is pure Go, standard library only: no go.sum full of third-party modules to vet.
Release binaries
Section titled “Release binaries”Every release ships prebuilt binaries for linux / macOS / windows on amd64 / arm64, each with:
- an SBOM (
*.sbom.json), and - a
checksums.txtsigned keyless via Sigstore/cosign.
Verify a download against the signed checksums (the exact command is printed in each release’s notes), then check the binary:
flareover versionVerifying the signature
Section titled “Verifying the signature”# from a release directory containing checksums.txt(.pem/.sig)cosign verify-blob \ --certificate checksums.txt.pem \ --signature checksums.txt.sig \ --certificate-identity-regexp 'https://github.com/fabriziosalmi/flareover' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com \ checksums.txtsha256sum -c checksums.txt --ignore-missingCredentials come from the environment
Section titled “Credentials come from the environment”flareover never takes secrets on the command line: every token is read from an environment variable, so nothing leaks via ps, /proc, or shell history. You’ll set these as you go (see Security for the full list); the first one you need is the read-only zone token:
export CLOUDFLARE_API_TOKEN=… # read-only, for `extract`Next: Quick Start.