Your own linter,
defined in YAML regex.
RegLint is a regex-based static analysis tool that ships as a single static Go binary. Write rules anyone can read, scan any language, and enforce them in CI — from one config file.
brew install reglint/tap/reglintcurl -fsSL https://raw.githubusercontent.com/reglint/reglint/main/install.sh | shgo install github.com/reglint/reglint/cmd/reglint@latestRules in plain YAML
A message, an RE2 regex, a severity — that's a rule. No DSL to learn, no server to run. Scope rules by glob, set severity levels, and fail builds with --fail-on.
Built for AI agents
Deterministic scans agents can trust and re-run. Scan only staged or added lines, suppress legacy findings with baselines, and let the reglint-setup skill configure everything.
CI gates without glue
Native GitHub PR annotations, SARIF for code scanning, JSON for machines — all from one binary. Or use the checksum-verified reglint-action and pin it in one step.
Why RegLint?
Between ad-hoc grep pipelines and heavyweight language analyzers sits the gap every team hits: rules you write yourself, enforced everywhere, today.
| grep + scripts | Secret scanners | Semgrep | RegLint | |
|---|---|---|---|---|
| Custom rules | Ad hoc pipelines | TOML rulesets | Per-language DSL | One YAML schema, every file type |
| Language coverage | Any text | Secret patterns only | One language per ruleset | Any text |
| Severity + fail threshold | DIY exit codes | Varies | Yes | Built in (--fail-on) |
| Baseline of known findings | No | Varies | Varies | Built in |
| PR annotations + SARIF | No | Varies | Extra tooling | Native output formats |
| Deployment | Your scripts | Single binary | Binary or server | Single static binary |
Enforce your first rule in two commands
reglint init writes a starter config with secret-detection rules. reglint analyze runs it. That's the whole onboarding.