oxlint-auto-configure

README

oxlint-auto-configure

Generate the optimal .oxlintrc.json — not a linter, a configurator.

This tool's one job: inspect your project and write the best possible oxlint config. It does not lint, fix, or replace oxlint — it configures oxlint so you don't have to.

Why

Oxlint has 870 rules across 7 categories and 15 plugins. Only 111 are enabled by default. Manually configuring each rule for maximum type safety is tedious and error-prone. This tool automates the entire process:

• Discovers your project type (React, Next.js, Vue, etc.)
• Enables relevant plugins automatically
• Sets optimal severity for every rule based on your chosen profile
• Generates a ready-to-use .oxlintrc.json

Scope boundary: This tool generates .oxlintrc.json. Running oxlint, auto-fixing code, and enforcing lint rules are oxlint's job. The analyze command is a diagnostic aid to help you decide which profile to use — not a replacement for running oxlint itself.

Installation

Nix (recommended)

# Build and run directly (oxlint included)
nix run github:larsartmann/oxlint-auto-configure -- configure

# Or install to your nix profile
nix profile install github:larsartmann/oxlint-auto-configure

# Dev shell with go, oxlint, gopls, golangci-lint
nix develop github:larsartmann/oxlint-auto-configure

Go

go install github.com/larsartmann/oxlint-auto-configure/cmd/oxlint-auto-configure@latest

Requires Go 1.26+ and oxlint in PATH.

Note: When building or running from source, set GOEXPERIMENT=jsonv2. The project uses encoding/json/v2, which is still behind the jsonv2 experiment in Go 1.26. Nix builds and dev shells set this automatically.

Quick Start

# Generate config with strict profile (default)
oxlint-auto-configure configure

# Maximum type safety — ALL rules at 'error'
oxlint-auto-configure configure --profile maximal-typesafe

# Dry run to see what would change
oxlint-auto-configure configure --dry-run

# Validate your existing config
oxlint-auto-configure validate

# Analyze project and show findings (SARIF output)
oxlint-auto-configure analyze

# Report of all 870 rules and their recommended severity
oxlint-auto-configure report

Profiles

Profile	Correctness	Suspicious	Style	Perf	Pedantic	Restriction	Nursery
maximal-typesafe	error	error	error	error	error	error	warn
strict	error	error	warn	warn	warn	warn	off
minimal	error	default	default	default	default	default	default

The former recommended profile was removed: it produced byte-identical output to strict. Scripts passing -p recommended get a migration error pointing at strict.

Profile Details

• maximal-typesafe: Every single rule at error. Maximum type safety and correctness enforcement. Even nursery rules at warn.
• strict (default): Core correctness at error, everything else at warn except nursery.
• minimal: Only correctness at error. Everything else uses oxlint defaults.

Project Detection

The tool auto-detects your project type and enables relevant plugins:

Detected	Plugins Enabled
React	react, jsx-a11y, react-perf
Next.js	nextjs, react, jsx-a11y, react-perf
Vue	vue
Jest	jest, node
Vitest	vitest, node
TypeScript	typescript (always on)

External JS Plugins (@shadcn/lint)

Oxlint JS plugins load at runtime from npm packages via the jsPlugins config key. This tool detects @shadcn/lint — the agent-first design-system linter for Tailwind v4 — and integrates it without ever fighting your design-system policy:

• Detect & register: when @shadcn/lint is in your package.json, the generated config registers it ("jsPlugins": ["@shadcn/lint"]). Requires oxlint >= 1.80; configure warns if the oxlint in PATH is older.
• Never enables rules: shadcn/* rules encode your design-system policy (contracts, allowlists, custom messages), so configure leaves them off and points you to the rule docs. Add them under rules yourself when ready.
• Preserves your setup: regenerating a config never destroys an existing @shadcn/lint setup — jsPlugins, every shadcn/* rule (verbatim, including options like ["error", {"allow": ["layout"]}]), and settings.shadcn all survive.
• Validates: validate accepts shadcn/* rules (reported as external, not unknown) and understands oxlint's array-form rule values.

Commands

configure

Generate the optimal .oxlintrc.json:

oxlint-auto-configure configure [flags]

Flag	Default	Description
-p, --profile	strict	Configuration profile
-c, --config	.oxlintrc.json	Output config file path
-d, --dry-run	false	Show changes without writing
--fix	false	Run oxlint --fix after writing config
--root	.	Project root directory

analyze

Run oxlint and show findings using the go-finding pipeline:

oxlint-auto-configure analyze [--root .] [-f summary|json|report|sarif|table]

validate

Validate an existing .oxlintrc.json:

oxlint-auto-configure validate [-c .oxlintrc.json]

report

Generate a report of all rules and recommended severities:

oxlint-auto-configure report [-p strict] [-f table|json|summary]

Rule Statistics

Category	Count	Default
Correctness	272	111 enabled
Style	280	mostly disabled
Pedantic	126	disabled
Restriction	103	disabled
Suspicious	63	disabled
Perf	15	disabled
Nursery	11	disabled
Total	870	111 enabled

Plugin	Rules
eslint	187
unicorn	138
vitest	72
react	63
jest	60
vue	46
jsx_a11y	36
import	33
oxc	26
jsdoc	22
nextjs	21
promise	16
typescript	110
node	9
react_perf	4

Development

GOWORK=off GOEXPERIMENT=jsonv2 go test -race ./...  # Run tests with -race
GOWORK=off GOEXPERIMENT=jsonv2 go vet ./...         # Run go vet
GOWORK=off GOEXPERIMENT=jsonv2 golangci-lint run ./...  # Run linter
nix build .                                          # Build via nix (runs tests)
nix run . -- configure                               # Run via nix (oxlint included)
oxlint -f json --rules > pkg/rule/rules_data.json  # Refresh rules from oxlint
GOWORK=off go mod vendor                             # Re-vendor deps (needed after go.mod changes)

Architecture

oxlint-auto-configure/
├── cmd/oxlint-auto-configure/   # CLI entry point
├── pkg/
│   ├── rule/                   # Rule types, registry (870 embedded rules)
│   ├── profile/                # Profiles, categorization engine
│   ├── config/                 # .oxlintrc.json generator
│   ├── detect/                 # Project type detection
│   ├── diff/                   # Config comparison
│   ├── format/                 # Findings rendering (summary, JSON, table)
│   ├── oxlint/                 # go-finding Detector for oxlint
├── internal/cli/               # CLI commands (Cobra)
└── docs/                       # Documentation

Tools Using This

• go-finding — Unified static analysis data model
• golangci-lint-auto-configure — Linter configuration for Go
• BuildFlow — Consumes pkg/provider (toolsdk Spec) to auto-generate missing oxlint configs before linting

License

MIT