Repository navigation
Invaris v0.5.0
Invaris v0.5.0
Invaris 0.5.0 closes the gaps found when Invaris was used on a real Node project: it is easier to discover, mutation harnesses can delete a line, common test reporters plug into mutation runs without a hand-written adapter, and guards can report richer findings.
invaris --help(also-handhelp) prints usage and exits0, andinvaris --version(alsoversion) prints the version.- Mutation (v1alpha3) harnesses accept
"operator": "delete", which removes the single occurrence ofbefore; omitafteror set it to"". See mutation operators andexamples/mutation/deleted.json. invaris test-result <go-test-json|jest-json|junit-xml> [FILE|-]convertsgo test -json, jest or vitest JSON, and pytest JUnit XML into theinvaris.test-result/v1alpha1object a mutation test command prints. It exits0when every test passed,1when an assertion failed and2when the run failed outside an assertion: a build failure, a timeout,TestMainexiting nonzero, a suite that failed to load or whoseafterAllthrew, or a pytest setup error. Exit2is an infrastructure failure, so it never counts as a killed mutant. Skipped tests are left out, so a skipped selected test makes the experiment inconclusive. See test-result converters.- Structured inspection findings accept optional
ruleId,messageandline. Reports carry the rule and an optionalline; the v1alpha5 portable profile still withholds messages. A challenge proof for a structured command guard matches the finding's policy and path, whateverruleIdthe guard reports. See inspection. - Campaign reports record the paths that harness
workspaceblocks left out of the snapshot (sourceIdentity.workspaceExclude) and a raised entry bound (workspaceMaxEntries), andinvaris explainreports them as theworkspace-excludedlimit. - Ecosystem publishes the Evaris compatibility table.
Default inputs, report versions and verification exit codes are unchanged, and the new fields are optional and omitted when unused. Consumers that strictly decode findings must accept the optional line before reading reports from guards that emit it: Evaris 0.4.0 accepts it, while Evaris 0.3.0 and earlier refuse such reports, so upgrade Evaris first or together with Invaris. A harness that uses delete needs 0.5.0; earlier binaries refuse it. Reports are not authenticated: matching hashes show that bytes are consistent, not who ran a check or how.
Known limitations:
test-resultsupports three reporter formats. Test IDs follow each reporter's naming (package.Test,file::full name,classname::name), sotestIdsmust use the converted IDs. Write jest or JUnit reports to stdout or to a path excluded byworkspace.exclude, so the report file is not a workspace change.- Excluded paths and dependencies remain outside the integrity check; campaign reports now list them, but a command can still change them without the run noticing.
- The self-check experiment has not been repeated with these features or by a second operator.
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.
See the changelog, installation guide, evidence reference and threat model.