oxAudit GitHub

Find the flaw. Keep the code on your machine.

oxAudit finds vulnerabilities and leaked credentials in source code, dependencies, binaries and container images. It runs as a desktop workbench and a command line over one engine, so a finding in CI and a finding on your laptop are the same finding.

Install the command line Read the source

Open source under Apache-2.0. No telemetry. Latest release v0.2.7.

checkout.py

Edit the code, then scan it. Nothing you type leaves this page.

This is a seven-rule toy written for this page. oxAudit itself ships 79 source rules, 14 infrastructure rules and more than 40 secret rules.

What it scans

Source code

79 dangerous-code patterns across JavaScript, TypeScript, Python, Java, Go, C, C++, C#, Kotlin, Swift, PHP, Ruby and Rust. Each maps to a CWE and comes with a fix.

Secrets, now and in history

More than 40 credential rules with entropy filtering and placeholder suppression. A history scan runs the same rules over every blob reachable from any Git ref.

Dependencies

Reads lockfiles for npm, Yarn, pnpm, Cargo, Go, pip, Poetry, Maven, Gradle, NuGet, Bundler, Composer and more, and checks every pinned package against OSV.

Binaries and firmware

Finds vulnerable components inside compiled binaries, archives, packages and firmware images with its own scanner. No database to download first.

Container images

Opens saved Docker and OCI images, reads their dpkg, apk and rpm package databases, and matches them against the right distribution release.

Infrastructure as code

14 misconfiguration rules for Dockerfiles, Terraform, Kubernetes manifests and GitHub Actions: unpinned images, public buckets, wildcard IAM, privileged containers.

Why trust it

  • It tells you how accurate it is. Detection quality is measured against a committed corpus and published per rule, including the numbers that are not flattering. CI fails if they regress.
  • Every finding says how far it was verified. "Syntax" means a parser confirmed the match sits in code, not a comment. "Text" means no grammar was available.
  • Scanning is local. oxAudit contacts NVD, OSV, CISA KEV, EPSS and Exploit-DB only for the features you invoke. There is no telemetry to opt out of.
  • Findings are ranked by what is exploitable for you. Known exploitation, predicted exploitation, public exploit code and whether your source calls the package are kept as four separate signals.
  • Dismissals are decisions. A suppressed finding stays in the report with its reason and its author, and it expires.
oxAudit desktop workbench showing a source scan: a list of eval() findings on the left and one finding's detail, evidence and review actions on the right
The Source Scan screen, with one finding open for review.

Sixty seconds on the command line

See what is in this project.

oxaudit-cli scan .

Put it in a pipeline. Failing the build is opt-in.

oxaudit-cli scan . --format sarif --output oxaudit.sarif --fail-on high

Meeting a backlog? Capture today once, on main.

oxaudit-cli scan . --format json --output baseline.json

Then fail a pull request only on what it added.

oxaudit-cli scan . --baseline baseline.json --fail-on-new high

Block secrets before they are committed.

oxaudit-cli hook install

Reports export as oxAudit JSON, SARIF 2.1.0, CycloneDX 1.6, SPDX 2.3, OpenVEX and CycloneDX VEX. Under GitHub Actions the command line annotates the pull request on its own.

Install

On macOS and Linux, the installer verifies the release checksum before it installs the command line.

curl -fsSL https://raw.githubusercontent.com/HenryCooper86/oxAudit/main/scripts/install.sh | sh

Download v0.2.7 Getting started guide

What the release ships
Command lineLinux x86_64 and aarch64, macOS universal, Windows x86_64
Desktop appLinux x86_64 packages. macOS and Windows build from source.
Container imagelinux/amd64 and linux/arm64, with the command line and the browser workbench server
EditorA VS Code extension that reports findings as diagnostics