Introducing CodeDig: Know What You're Shipping

Today we are launching CodeDig — a developer tool that analyzes every pull request for risk, security vulnerabilities, and architectural impact before it reaches production.

The Problem

Every engineering team has experienced the same story: a seemingly harmless PR gets merged, and hours later something breaks in production. The change looked small — a few files, a minor refactor — but it touched a critical path that dozens of downstream services depend on.

Traditional code analysis tools scan your repository on a schedule, flagging issues long after the code has shipped. By the time you see the report, the damage is done. What teams need is analysis at the moment of decision: when a pull request is open and the reviewer is deciding whether to approve.

What CodeDig Does

CodeDig installs as a GitHub App in a single click. No config files, no CI pipeline changes. The moment a pull request is opened, CodeDig analyzes the diff and posts a detailed comment with:

• Risk score — A composite score based on blast radius, complexity delta, and historical failure patterns. High-risk PRs get flagged before they cause incidents.
• Blast radius mapping — See exactly which downstream services, consumers, and APIs are affected by the change.
• Security scanning — 200+ rules covering OWASP Top 10 categories, hardcoded secrets, SQL injection, PII exposure, and language-specific pitfalls.
• Test coverage gaps — Overlay coverage data on the diff to see which new or changed code paths lack tests.
• Architectural intelligence — Detect boundary violations, unwanted coupling, and drift from your declared architecture rules.

Multi-Language, Zero Config

CodeDig provides deep, language-aware analysis for C#, TypeScript, Rust, Python, Java, and Go. The same rich insights regardless of which language a PR touches — all from a single install.

Get Started

CodeDig is available today with a free tier that includes 1 repository and 30 PRs per month. Install the GitHub App and start analyzing your next pull request in under 60 seconds.