How does GauntletCI compare to SonarQube?

SonarQube analyzes the entire codebase on a schedule and requires a server, account, and network access. GauntletCI analyzes only the lines that changed in the current diff, runs entirely on the developer's machine in under one second, requires no account or cloud connection, and installs as a pre-commit hook. SonarQube is a full codebase quality platform; GauntletCI is a focused change-risk detector that runs before a commit is ever created.

How does GauntletCI compare to Semgrep?

Semgrep is a pattern-matching engine that scans files or the full codebase. GauntletCI scopes every rule to the changed diff, meaning it only flags risks introduced by the current change, not pre-existing issues in unchanged files. GauntletCI also includes incident correlation, local LLM enrichment, and baseline delta mode, which Semgrep does not offer. GauntletCI's free tier includes all rules with no account required.

How does GauntletCI compare to Snyk?

Snyk is primarily a dependency and container vulnerability scanner that requires cloud connectivity and a Snyk account. GauntletCI detects behavioral, structural, and security risks in first-party code changes, not dependency vulnerabilities, and runs 100% locally with no data transmitted. GauntletCI is suitable for air-gapped environments and organizations with strict data residency requirements; Snyk is not.

How does GauntletCI compare to CodeQL / GitHub Advanced Security?

CodeQL performs deep semantic analysis of the full codebase and requires compilation and significant compute time, typically minutes per run. GauntletCI analyzes only the changed diff in under one second with no compilation step, making it suitable as a pre-commit hook in the developer's local workflow. CodeQL is better for periodic deep security audits; GauntletCI is better for fast, continuous feedback on every commit.

How does GauntletCI compare to Code Climate?

Code Climate is a SaaS platform that analyzes full repositories for maintainability and test coverage trends over time. It requires uploading code to a cloud service. GauntletCI is fully local, diff-scoped, and focused on change risk rather than codebase health metrics. GauntletCI does not require a cloud account, never transmits code, and produces results in under one second, making it a complement to, not a replacement for, Code Climate's longitudinal reporting.

Does GauntletCI work in air-gapped or offline environments?

Yes. GauntletCI runs entirely on the local machine. No diff, finding, file path, or telemetry is transmitted. The optional local LLM enrichment feature (--with-llm) uses a locally hosted Ollama model, with no network call. This makes GauntletCI suitable for classified, regulated, or air-gapped environments where cloud-based analysis tools are prohibited.

What is baseline delta mode and do other tools offer it?

Baseline delta mode (gauntletci baseline capture) snapshots all current findings and suppresses them from future runs. Only net-new findings (risks introduced after the baseline) are reported. This eliminates alert fatigue from pre-existing issues in legacy codebases. SonarQube offers a similar 'new code' concept but requires server setup. Semgrep, Snyk, CodeQL, and Code Climate do not offer equivalent pre-commit baseline suppression.

How do I install the GauntletCI Neovim plugin?

With lazy.nvim: add { 'EricCogen/GauntletCI-Neovim', ft = { 'cs' }, opts = { sensitivity = 'balanced' } } to your plugin list. With packer: use 'EricCogen/GauntletCI-Neovim' and call require('gauntletci').setup() in your config.

What Neovim version is required?

Neovim 0.9 or later. The plugin uses vim.diagnostic, which was stabilized in 0.6 but 0.9 is recommended for the best experience.

How do I run analysis in Neovim?

Run :GauntletCIAnalyze to analyze the current commit. Findings appear as native vim.diagnostic entries. Clear them with :GauntletCIClear.

Can analysis run automatically on save?

Yes. Set analyze_on_save = true in your setup() call. This runs analysis whenever a .cs file is saved, which may add a brief delay on large repositories.

Extensions

Neovim Plugin

The GauntletCI Neovim plugin runs behavioral change risk detection on .NET commits and surfaces findings as native vim.diagnostic entries - visible in the sign column, virtual text, and the diagnostics float.

Requirements

Neovim 0.9 or later
GauntletCI CLI: dotnet tool install -g GauntletCI

Install

lazy.nvim

{
  "EricCogen/GauntletCI-Neovim",
  ft = { "cs" },
  opts = {
    sensitivity = "balanced",
    analyze_on_save = false,
  },
}

packer.nvim

use {
  "EricCogen/GauntletCI-Neovim",
  config = function()
    require("gauntletci").setup({
      sensitivity = "balanced",
      analyze_on_save = false,
    })
  end,
}

Commands

Command	Description
:GauntletCIAnalyze	Run analysis on the current commit.
:GauntletCIClear	Clear all GauntletCI diagnostics.

Diagnostic output mockup

OrderService.cs

40Epublic decimal CalculateTotal(Order order)

41 {

42E return order.Lines.Sum(l => l.Price * l.Qty);-- GCI0001: Logic change without test coverage

43W if (order.Discount > 0)-- GCI0012: Exception path without null guard

Configuration

require("gauntletci").setup({
  -- Path to gauntletci executable (default: "gauntletci", must be on PATH)
  executable = "gauntletci",
  -- "strict" | "balanced" | "permissive"
  sensitivity = "balanced",
  -- Run automatically when a .cs file is saved
  analyze_on_save = false,
  -- Disable LLM enrichment for fast local analysis
  no_llm = true,
})

Recommended keymaps

vim.keymap.set("n", "<leader>ga", "<cmd>GauntletCIAnalyze<cr>",
  { desc = "GauntletCI: analyze" })
vim.keymap.set("n", "<leader>gx", "<cmd>GauntletCIClear<cr>",
  { desc = "GauntletCI: clear" })

Troubleshooting

No diagnostics after :GauntletCIAnalyze

Analysis runs against the most recent commit. Check :messages for any error output from the plugin. Run gauntletci analyze --staged in a terminal to confirm the CLI works independently.

CLI not found

Neovim may not inherit your shell PATH on macOS/Linux when launched from a GUI. Either set executable = "/full/path/to/gauntletci" in your setup call, or ensure Neovim is launched from a shell that has the dotnet tools directory in PATH.

Source and releases

Source code and releases are at EricCogen/GauntletCI-Neovim.