panic-attack provides static analysis and optional stress testing. A scan result is evidence within its reported coverage, not a certificate that a project is safe.
Install Rust and Cargo using your preferred tool manager. The default CLI’s
minimum Rust version is declared in Cargo.toml (rust-version, currently 1.90).
Use a compatible compiler rather than updating every language toolchain.
The optional GUI has additional compiler and system-library requirements.
Scanning a language does not require installing that language’s compiler.
The following commands assume a POSIX shell, Git, Zig configured to compile
native C dependencies through zig cc, a working native linker, and access
to the pinned dependencies. The default build compiles C sources from
tree-sitter-php. Installing Zig alone does not select it for Cargo’s native
dependency build scripts; configure their C compiler before building.
These commands do not require just, mise, or Guix.
git clone https://github.com/hyperpolymath/panic-attack.git
cd panic-attack
cargo build --locked --release
./target/release/panic-attack --help
./target/release/panic-attack assail . --fail-on-incomplete --output panic-report.jsonA self-scan can return findings or incomplete coverage, including from deliberate
test fixtures. Do not interpret a nonzero scan exit as an installation failure;
inspect panic-report.json for individual findings and the coverage outcome.
With just installed, just --list lists the actual recipes. just install
builds the default release CLI and copies it to $HOME/.local/bin, creating
that directory if needed. Add that directory to PATH yourself if desired.
This recipe does not install prerequisites or offer a portable/prefix option.
just doctor checks whether Cargo, rustc, Git and just can run. It returns
nonzero for a missing or broken tool. It does not check compiler compatibility,
network connectivity, runtime safety, or prove a build will succeed.
Use the locked build above to check compiler and dependency compatibility.
The probe disables automatic toolchain installation with rustup 1.28.1 and
later. Older rustup versions and external tool-manager shims may still perform
their own setup; the diagnostic is not a sandbox around those programs.
Record the failing command and its exit code before changing toolchains. Report problems at https://github.com/hyperpolymath/panic-attack/issues with the relevant error text. Review any local paths or sensitive details before sharing logs. Platform details are optional.
The legacy setup.sh still installs just through platform package managers;
it is not the cross-platform provisioning interface proposed for the estate.
The direct build path above avoids those automatic package-manager changes.
The existing heal recipe is not a targeted dependency repair service.
Do not use it as a substitute for diagnosing a failed build.
There are no stapeln-run, run, or uninstall recipes in this checkout.
To remove a user-local installation, remove only the binary you installed.
See README for features and analysis limitations.