zuit

Quality dimensions

zuit emits an independent 0–100 score across 9+ quality dimensions. Below are the five core dimensions every project gets; supply chain, packaging, performance, and health dimensions kick in when their language frontend is enabled.

Maintainability

Length, nesting, branching — how easy the code is to change.

Security

Hardcoded secrets, eval sinks, unsafe blocks.

Complexity

Project-level fan-out and dependency cycles.

Documentation

Public-API doc coverage and TODO/FIXME inventory.

Test smell

Test ratio, missing assertions, skipped tests.

How teams use zuit

Three common flows. Pick the one that matches today's problem.

Local dev loop

Watch mode and LSP underline findings as you type — no CI round-trip.

CI quality gate

Fail builds when findings cross a severity threshold. Upload SARIF to GitHub code scanning.

Legacy adoption

Baseline existing findings so CI only fails on what's new.

Pipeline at a glance

Every zuit analyze run follows five deterministic stages. Output is sorted by (file, span, rule_id) — two runs against unchanged source produce byte-identical output.

Quick start

cargo install --locked zuit
zuit analyze .

See Quickstart for build-from-source and CI usage.