Swift validator
Mature Swift projects need precision and appropriate abstention. Axint separates deterministic findings from probable static evidence and non-blocking review leads, then lets successful Xcode evidence suppress claims that the compiler has already contradicted.
existing project
$axint prove --dir /path/to/MyAppevidence
compiler dominates
mode
brownfield-safe
output
signed receipt
01
A finding carries confidence, evidence state, blocking behavior, and provenance. Confirmed failures can stop the run. Probable findings explain what evidence is still missing. Advisory findings remain review leads. Suppressed findings stay visible in the receipt without blocking a project whose stronger evidence passed.
02
Existing teams can run a local-only, advisory, no-fix integration that creates no source, installs no project instructions or memory, makes no network request, and writes artifacts only where the user selects.
03
Axint publishes a labeled paired-case benchmark for precision, recall, and clean-project abstention. The benchmark is deliberately inspectable and release-gated; it is evidence about the included corpus, not a claim that every private project will behave identically.
common questions
No. Advisory findings are non-blocking, and stronger compiler or build evidence can suppress contradicted compiler-shaped claims.
Yes. The prove and minimal integration paths are designed for existing Swift and Xcode projects.
continue