Documentation
DACIP is a deterministic contract gate: it reads both sides of every boundary in your codebase — routes and the calls that target them, env vars, GraphQL, migrations, feature flags, and more — and proves what a change breaks, with a repro per finding and no LLM anywhere in the pipeline.
Two ways in: the quickstart gets you from zero to a first finding in about thirty seconds on any public repo; the GitHub App puts the same engine on every pull request. If you ship with a coding agent, start with the Claude Code integration.
Quickstart
From zero install to your first verified finding in about 30 seconds.
Get startedGitHub App
The PR gate — one check run, one comment, SARIF to code scanning, and nothing when your PR is clean.
Get startedClaude Code integration
Install DACIP into a repo so Claude Code gets verified facts over MCP and a pre-write guardrail that denies contract-breaking edits.
ReferenceCLI reference
Every dacip subcommand, its flags, and exit codes.
ReferenceWhat DACIP checks
All 22 analyzers, grouped by boundary — what each compares, its finding codes, and when it stays silent.
ConceptsFindings & evidence
How DACIP grades severity and confidence, when a defect is asserted vs. demoted to an observation, and how every claim carries a runnable proof.
ConceptsCoverage & the honest ceiling
How DACIP reports what it could not see — coverage counts, partial routes, dynamic paths, and the TS analyzer requirement.
ConceptsDeterminism
Same two commits in, byte-identical verdict out — no LLM in the pipeline, proved nightly in public.
AccountLicensing & the trial
How free and paid work mechanically — the public-repo check, the one-repo trial meter, offline licenses, and seat pricing.
HelpTroubleshooting
The problems DACIP users actually hit, each with the fix.