Skip to content

JevGate 0.18.0

Choose a tag to compare

@github-actions github-actions released this 26 Sep 02:08
· 468 commits to main since this release
curl -fsSL https://raw.githubusercontent.com/Tech-Byte-Frontier/jevgate/v0.18.0/install.sh | sh
cargo binstall jevgate   # or: cargo install jevgate --locked

Verify a download with gh attestation verify <archive> --repo Tech-Byte-Frontier/jevgate.

  • Documentation site: https://tech-byte-frontier.github.io/jevgate/, with guides, troubleshooting, a page on coding agents, and rules, configuration and command-line references generated from the binary. It is published with each release.
  • Homebrew: brew install tech-byte-frontier/tap/jevgate installs the release binaries on macOS and Linux, and each release updates the formula.
  • --format sarif writes a SARIF 2.1.0 log for GitHub code scanning, GitLab and editors: the findings --format github annotates, as error when they fail the gate and warning otherwise, with every rule's question, related locations, the finding's fingerprint and probability. Run errors and files that could not be judged are tool notifications.
  • --format gitlab writes a GitLab Code Quality report, so merge requests show the findings: the ones --format github annotates, major when they fail the gate and minor otherwise, with JevGate's fingerprints.
  • jevgate completions SHELL prints a completion script for bash, zsh, fish, elvish or PowerShell, and jevgate man [COMMAND] a man page, both generated from the same definitions as --help. The Homebrew formula installs them.
  • Agent output is colored on a terminal: the headline by the gate's outcome, review and consider headings, and each finding's location. --color auto|always|never chooses, and NO_COLOR and CLICOLOR_FORCE are honored; JSON and GitHub annotations are never colored.
  • pre-commit hooks: jevgate-system runs the installed jevgate on the staged changes, and jevgate builds it from source with Rust first.
  • jevgate.schema.json is a JSON Schema of jevgate.toml, generated from the configuration types with every rule name and level, and jevgate init writes a #:schema line so editors with TOML schema support complete and check the file.