Repository navigation
Invaris v0.3.0
Invaris v0.3.0
Invaris 0.3.0 makes harnesses easier to create and upgrade, adds three deterministic guard-challenge operators, and provides portable evidence for sharing results.
invaris initdetects project markers and creates a generic or Go starter harness without running project code or overwriting a file.invaris migrateupgrades v1alpha1 harnesses to v1alpha2 while preserving commands and effective gates. Preview with--dry-run; a write keeps an exact.bakfile.checkandchallengesupport--format text|compact; campaigns also support compact output. JSON remains the default and report files remain JSON.- v1alpha4 guard harnesses can name
trailing-whitespace,crlf-injectionandsecret-leak-injection, pinned to an exact preimage. Built-in edits require structured detection evidence. - v1alpha5 evidence adds mutation metadata, reproduction identities, command digests and campaign effectiveness rows while withholding machine paths, command arguments, output and free-text details. It is automatic for v1alpha4 harnesses and opt-in for older inputs with
--evidence-version v1alpha5. - Workspace preparation now stops on cancellation, removes partial copies and records cancellation or timeout as the outcome reason.
Existing harnesses retain their default report versions and exit codes. A v1alpha4 harness needs a 0.3.0 binary; older binaries refuse it. Migration changes the config digest and reports compatibility as native. The fixed synthetic secret is a test fixture, not a working credential, and requires a scanner rule that recognizes it.
Linux and macOS archives for amd64 and arm64 include both invaris and invaris-command-provider, a README and the Apache-2.0 license. Verify downloads with SHA256SUMS. No Go installation is needed to run the binaries; source builds require Go 1.27.4 or later. Windows is supported through WSL using the Linux archives.
Commands run with your user permissions and can access the network and external files. Disposable copies are not security sandboxes. IDs and configured target names remain visible in portable evidence; neither hashes nor reports authenticate who ran a check.
See the changelog, installation guide, authoring guide, operator catalog, evidence reference and threat model.