Know the blast radius of every PR before you merge

CodeDig helps reviewers understand PR risk, blast radius, test gaps, and security-relevant changes before they approve the merge.

A
codedig-botcommented 2 minutes ago
bot
CodeDig PR Analysis — Medium Risk (Score: 62/100)

Summary

MetricValue
Files Changed12
Blast Radius47 downstream consumers
Test Coverage on Changed Paths23%
Public API Changes3 breaking
Security Findings1 (SQL injection risk)

⚠️ Key Findings

  • 3 public API changes detected — 47 downstream consumers affected
  • Payment processing module changed with 0% test coverage
  • New SQL query without parameterized inputs (line 142)

Recommendations

  • Add tests for PaymentProcessor.processRefund()
  • Use parameterized query in UserRepository.findByEmail()
  • Update API documentation for breaking changes

Up and running in 3 steps

  1. 1

    Install the GitHub App

    1 click to connect your repositories. No config files, no CI changes.

  2. 2

    Open a Pull Request

    CodeDig automatically analyzes every PR the moment it is opened.

  3. 3

    Review with Confidence

    See risk scores, blast radius, and recommendations inline on every PR.

PR risk signals reviewers can act on

Keep the product centered on the decision reviewers make every day: is this PR safe enough to merge?

PR Risk Analysis

Every PR gets a risk score based on blast radius, test coverage gaps, and complexity changes. High-risk PRs are flagged before reviewers approve the merge.

Security Scanning

Automatic detection of PII exposure, SQL injection, hardcoded secrets, and OWASP Top 10 vulnerabilities in every code change.

Architectural Intelligence

Track architectural drift, detect dead code, and understand how your codebase evolves over time with time-travel analysis.

Security findings in the PR review flow

CodeDig checks changed code for hardcoded secrets, SQL injection, PII exposure, and security-relevant patterns. Findings appear inline on the PR with severity and remediation guidance.

Security Findings

5 issues found
SeverityFindingFile
CriticalHardcoded AWS secret keysrc/config/aws.ts
HighSQL injection in query buildersrc/db/queries.ts
MediumPII exposure in log outputsrc/utils/logger.ts
MediumMissing CSRF token validationsrc/api/auth.ts
LowOutdated dependency (lodash 4.17.20)package.json

Pricing for PR risk analysis

Analyze your first repository free, then scale PR-risk coverage across the team.

Free

$0/mo

  • Repos3
  • PRs analyzed/mo50
  • Users3
  • PR risk analysis
  • Security scanningBasic
  • Test gap analysis
  • Architectural drift
  • Time-travel analysis
  • Data retention30 days
  • SupportCommunity
Analyze a PR free
Recommended for teams

Team

$49/mo

  • Repos10
  • PRs analyzed/mo500
  • Users15
  • PR risk analysis
  • Security scanningFull
  • Test gap analysis
  • Architectural drift
  • Time-travel analysis
  • Data retention90 days
  • SupportEmail
Start 14-day trial

Business

$199/mo

  • ReposCustom
  • PRs analyzed/mo5,000
  • UsersCustom
  • PR risk analysis
  • Security scanningFull
  • Test gap analysis
  • Architectural drift
  • Time-travel analysis
  • Data retention1 year
  • SupportPriority
Start 14-day trial

Enterprise

Custom

SSO, deployment reviews, dedicated support, custom SLAs, and security review support for larger organizations.

Book demo

Need a team walkthrough?

Want to review a real PR workflow, data handling, or enterprise rollout requirements? Book a call or send us a message.

or fill out the form below

< 30s

Typical Small/Medium PR Analysis

Zero

Config Files Required

6+

Languages Supported

Timing and language coverage reflect current product targets and internal testing; results vary by repository size and configuration.