One binary
Trivy and Gitleaks are built in as Go libraries, so there is no Docker daemon, no Python and no external CLI. Run it and the web UI opens in your browser.
Scan your repos for vulnerabilities and leaked secrets, on your own machine.
Free & open source · One binary, no Docker · macOS, Linux, Windows
Trivy and Gitleaks are built in as Go libraries, so there is no Docker daemon, no Python and no external CLI. Run it and the web UI opens in your browser.
Every finding comes with the fixed version that closes it. Results from all scanners land in one normalized, filterable report.
Gitleaks checks the working tree. Matches are stored redacted with an HMAC, so the same secret is recognised across scans but never kept in plain text.
Licence issues and infrastructure-as-code misconfigurations (Terraform, Kubernetes, Dockerfiles and more) show up next to the vulnerabilities.
Connect a read-only GitHub token (kept in the OS keychain), pick repositories and scan. No GitHub? Point it at any directory instead.
bastion scan prints JSON, a table or SARIF. --fail-on exits 2 at your severity threshold, so CI can tell "findings" from "the scan broke".
Hide a finding as ignored, accepted risk or false positive. A reason is required, and the decision carries over to later scans of that project.
Loopback only, a single-use startup token, a DNS-rebinding guard, CSRF protection and a strict Content-Security-Policy.
No analytics, no update check. The only network calls are the vulnerability database downloads and the GitHub requests you trigger.

macOS or Linux, with Homebrew:
brew install ozerozdas/tap/bastion
macOS or Linux, without Homebrew (checks the sha256 before installing):
curl -fsSL https://raw.githubusercontent.com/ozerozdas/bastion/master/install.sh | sh
Windows builds and every archive are on the latest release page. The binary is ~156 MiB; the first scan also downloads a ~1.7 GB vulnerability database into the cache directory.
Run it. It binds 127.0.0.1 on a random port and opens your browser:
bastion
In CI, write SARIF and fail the build on critical findings:
bastion scan --path . --no-store \ --format sarif --fail-on critical > bastion.sarif
mirror.gcr.io / ghcr.io — on the first scan, then on refresh (~1.7 GB)
api.github.com — only when you test, list, add or scan a repo
codeload.github.com — the repository tarball itself
Apache-2.0 licensed. v0.1 is in progress: container images, fix plans and SAST come next. Contributions welcome.