Skip to content

Free to run,no account needed

NHI-Blast is open source under the MIT License. Pick the way that suits your machine. Installing needs a package index once; every scan after that is offline.

Python 3.12 or later

From source

Linux, macOS or Windows with Python

  • Tested on Python 3.12, 3.13 and 3.14
  • The [hcl] extra adds the Terraform HCL fallback
  • Add -c requirements.lock to pin exact versions
Install
git clone https://github.com/DKtech-dev/nhi-blast.gitcd nhi-blastpython -m venv .venv.venv/bin/python -m pip install ".[hcl]"
Windows x64

Windows executable

One file, nothing else to install

  • No Python, pip or administrator rights needed
  • Check the SHA-256 record before you run it
  • Unsigned, so SmartScreen may warn the first time
Verify in PowerShell
$record = (Get-Content .\nhi-blast-windows-x64.exe.sha256 -Raw).Trim()$actual = (Get-FileHash .\nhi-blast-windows-x64.exe -Algorithm SHA256).Hash.ToLower()if ($record -ne "$actual  nhi-blast-windows-x64.exe") { throw "checksum mismatch" }
Run
nhi-blast-windows-x64.exe --helpnhi-blast-windows-x64.exe versionnhi-blast-windows-x64.exe scan . --format html --out nhi-blast-out
Download from the v0.3.0 release
Either install above

Reference fixture

See a full report in a minute

  • Synthetic data only, nothing real to leak
  • Prints the console summary and writes report.html
  • Exits 1 because findings meet --fail-on high
Scan fx07-incident
nhi-blast scan tests/fixtures/fx07-incident \  --simulate-compromise action:tj-actions/changed-files@v45 \  --format console --format html \  --fail-on high --out nhi-blast-out

On Windows from source, use .venv\Scripts\python.exe. Test only synthetic fixtures or repositories you are authorised to assess.

Good to knowbefore your first scan

What do I point it at?

The root of a repository. NHI-Blast reads the GitHub Actions workflows and the local composites and reusable workflows they call, Terraform plan or state JSON (with a best-effort HCL fallback) and IAM policy JSON. It needs no cloud credentials, and it never reads secret values, environment values or runner state.

How do I simulate a compromise?

Pass one or more selectors to --simulate-compromise. Each one is a scenario, and an invalid selector is a usage error.

action:OWNER/REPO[/PATH]@REF
A mutable third-party action at one reference, at every use site.
action-any:OWNER/REPO
The same action at any reference.
job:RELPATH#JOB_ID
One job in one workflow file.
workflow:RELPATH
Every job in a workflow file.
secret:NAME
A job and the secret reference it holds.
role:ROLE_ID_OR_TF_ADDRESS
An AWS role by graph id, ARN or Terraform address.
repo-write
A repository writer who can push a branch and edit a workflow.
fork-pr
A fork pull-request author whose code runs in a pull-request context.
all-mutable-actions
One scenario per mutable third-party action. Also drives rank.
Which commands are there?
nhi-blast scan PATH
Parse the files, audit OIDC trust, run scenarios and emit findings.
nhi-blast rank PATH
Rank mutable third-party actions by potential blast radius.
nhi-blast explain ID --report FILE
Print the evidence chain for a finding, node or edge.
nhi-blast export PATH --format json|dot
Export the authority graph.
nhi-blast diff BASE HEAD
Compare two saved reports: new, changed, unchanged, resolved or not observed.
nhi-blast baseline accept|prune
Record or remove reviewed diff suppressions, with a reason and a reviewer.
nhi-blast whatif REPORT --plan PLAN
Model containment offline and write whatif.json and playbook.md.
nhi-blast schema
Print the report JSON Schema.
nhi-blast version [--data]
Print the tool, schema and data-file versions.
What do the exit codes mean?
0
Success
1
Findings at or above --fail-on
2
Usage or input error
3
Partial results with --strict
4
Unexpected internal error
Can I configure it?

An nhi-blast.toml in the scan root loads on its own, and --config picks another file inside the root. Unknown keys are rejected, so a typo cannot quietly change a result. Bindings hold role identifiers, never credential values.

nhi-blast.toml
repo_slug = "acme/shop"default_branch = "main"aws_account = "111122223333"aws_region = "us-east-1"[bindings.roles]AWS_ROLE_ARN = "arn:aws:iam::111122223333:role/deploy-prod"[ignore]rules = ["NHB-GHA-003"]paths = ["docs/examples/**"]
Does anything leave my machine?

No. Scanning makes no network requests and runs none of the content it reads, and the HTML report opens straight from the folder with no network at all. Credential values are never stored, printed, logged or embedded.

Can I rely on it in production?

Not yet. Version 0.3.0 is a public beta for testing and evaluation, not a production security control, and no independent security audit has been performed or is claimed. Treat every result as evidence to verify, and read the known limitations before relying on a finding.

Stuck, or found something odd?

Bugs belong in the beta bug report on GitHub. For anything else, from evaluating it with your team to plain feedback, write to us.