Why DORA metrics matter

Google's 2024 DORA Report (32,000+ respondents, 10 years of data) quantifies the gap between elite and low-performing engineering teams:

Metric	Elite teams	Low performers	Gap
Deploy Frequency	On-demand (multiple/day)	< once per 6 months	973×
Lead Time for Changes	< 1 hour	1 – 6 months	6,570×
Change Failure Rate	0–15%	46–60%	—
Time to Restore	< 1 hour	1 week – 1 month	6,570×

Elite teams are 2× more likely to meet reliability targets and 1.8× more likely to meet business goals (DORA 2024). delivery-intel tells you exactly where your team stands — in one command.

⚡ Quick Start

npx delivery-intel facebook/react

  ┌─────────────────────────────────────────────────────────┐
  │  📡 Delivery Intel  — Cyber-Diagnostic Report 2026      │
  └─────────────────────────────────────────────────────────┘

  Repository    facebook/react
  Scanned       2026-04-17T12:00:00.000Z

  ╭─────────────────────────────────────────────────────╮
  │  ⬡  Overall Health Score                            │
  │                                                     │
  │  ██████████████████████████░░░░  87/100  EXCELLENT  │
  ╰─────────────────────────────────────────────────────╯

  ◈  DORA Metrics
  ────────────────────────────────────────────────────────

  Deploy Frequency     ★ Elite
  12.4 deployments/week  (merged PRs)
  Last 7 days  ▃▄▅▆▇█▇

  Lead Time            ★ Elite
  3.2 hours median  (0.1 days)

  Change Failure Rate  ● High
  4.8%  (2 failed / 42 total runs)

  ◈  Vulnerability Scan  (OSV.dev)
  ────────────────────────────────────────────────────────
  ✓ No known vulnerabilities found

  ◈  Suggestions
  ────────────────────────────────────────────────────────
  ✓ Looking good, no critical issues detected

Works with full URLs too: npx delivery-intel https://github.com/vercel/next.js

🔍 What It Measures

Supports package.json, requirements.txt, and go.mod for vulnerability scanning.

🚀 Usage

CLI (zero install)

# Any public repo — no token needed
npx delivery-intel facebook/react

# Compare last 30 days vs prior 30 days
npx delivery-intel vercel/next.js --trend

# Include burnout risk score
npx delivery-intel vercel/next.js --risk

# AI-powered executive narrative (requires LLM key — falls back to template)
npx delivery-intel vercel/next.js --narrative

# JSON output
npx delivery-intel vercel/next.js --json

# Save report to file
npx delivery-intel vercel/next.js --json --output report.json

All flags

Web Dashboard

git clone https://github.com/ParthibanRajasekaran/delivery-intel.git
cd delivery-intel
npm install
npm run dev
# → http://localhost:3000

Paste a repo URL and get an animated dashboard with score ring, DORA cards, charts, vulnerability table, and suggestions. Dark theme with smooth animations.

Docker

# Dashboard
docker compose up dashboard

# CLI
REPO=facebook/react docker compose run --rm cli

📦 JSON Output Schema

Pass --json (or --json --output report.json) to get machine-readable output.

{
  "repo": { "owner": "vercel", "repo": "next.js" },
  "fetchedAt": "2026-04-17T12:00:00.000Z",
  "overallScore": 87,                          // 0–100
  "doraMetrics": {
    "deploymentFrequency": {
      "deploymentsPerWeek": 12.4,
      "rating": "Elite",                       // Elite | High | Medium | Low
      "source": "merged_prs_fallback"          // deployments_api | merged_prs_fallback
    },
    "leadTimeForChanges": {
      "medianHours": 3.2,
      "rating": "Elite"
    },
    "changeFailureRate": {
      "percentage": 4.8,
      "failedRuns": 2,
      "totalRuns": 42,
      "rating": "High"
    }
  },
  "vulnerabilities": [
    {
      "packageName": "lodash",
      "currentVersion": "4.17.15",
      "vulnId": "GHSA-xxxx-xxxx-xxxx",
      "summary": "Prototype pollution",
      "severity": "high",                      // critical | high | medium | low
      "aliases": ["CVE-2021-23337"],
      "fixedVersion": "4.17.21"
    }
  ],
  "suggestions": [
    {
      "category": "reliability",               // performance | reliability | security
      "severity": "high",                      // high | medium | low
      "title": "High Pipeline Failure Rate",
      "description": "...",
      "actionItems": ["..."]
    }
  ],
  "dailyDeployments": [0, 1, 2, 3, 1, 2, 3], // last 7 days, index 0 = 6 days ago
  // present only with --trend
  "trend": {
    "windowDays": 30,
    "current":  { "deploymentsPerWeek": 12.4, "leadTimeHours": 3.2, "changeFailureRate": 4.8, "score": 87 },
    "prior":    { "deploymentsPerWeek": 9.1,  "leadTimeHours": 5.6, "changeFailureRate": 6.2, "score": 78 },
    "deltas":   { "deploymentsPerWeek": 3.3,  "leadTimeHours": -2.4, "changeFailureRate": -1.4, "score": 9 }
  },
  // present only with --risk
  "riskScore": {
    "score": 42,
    "level": "moderate",                       // low | moderate | high | critical
    "cycleTimeDelta": 0.12,
    "failureRateDelta": -0.05,
    "sentimentMultiplier": 1.0,
    "summary": "..."
  }
}

🔐 Authentication

Token resolution order: --token flag → GITHUB_TOKEN env → gh auth token

Private repos require a token with repo scope. For CI, use ${{ secrets.GITHUB_TOKEN }}. It's auto-scoped and expires per job.

🔄 CI Integration

GitHub Actions Marketplace action

The easiest way — use the action directly from the Marketplace:

# .github/workflows/delivery-intel.yml
name: Delivery Intelligence

on:
  push:
    branches: [main]
  pull_request:

jobs:
  analyze:
    runs-on: ubuntu-latest
    steps:
      - uses: ParthibanRajasekaran/delivery-intel@main
        with:
          fail-below: '40'   # fail the job if score drops below 40

Outputs available after the step: score, deploy-frequency, lead-time, change-failure-rate, mean-time-to-restore.

npx (custom pipeline)

    steps:
      - name: Run delivery-intel
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: npx delivery-intel@latest ${{ github.repository }} --json --output report.json

      - name: Check health score
        run: |
          SCORE=$(jq '.overallScore' report.json)
          echo "Health score: $SCORE / 100"
          if (( $(echo "$SCORE < 40" | bc -l) )); then
            echo "::error::Score $SCORE is below threshold (40)"
            exit 1
          fi

A ready-to-use workflow file with PR comments and artifact upload is included at .github/workflows/delivery-intel.yml.

🏅 Badge

Once you have the dashboard deployed, you can show a live delivery score in any README:

[![Delivery Score](https://your-deployment-url/api/badge?repo=owner/repo)](https://github.com/ParthibanRajasekaran/delivery-intel)

The GET /api/badge?repo=owner/repo endpoint returns a Shields.io endpoint-badge payload. Score maps to color: < 20 red → < 40 orange → < 60 yellow → < 80 green → ≥ 80 bright green. Results cached 5 minutes.

Self-hosting: deploy the dashboard (npm run build && npm start or docker compose up dashboard) and replace your-deployment-url.

🏗️ Architecture

┌──────────────────────────────────────────────────────────────┐
│                      delivery-intel                          │
├──────────────┬───────────────┬───────────────────────────────┤
│   CLI        │   Dashboard   │   CI Workflow                 │
│  (npx)       │  (Next.js)    │   (.github/workflows/)        │
├──────────────┴───────────────┴───────────────────────────────┤
│                  Shared Analysis Engine                       │
├──────────┬────────────┬──────────────┬───────────────────────┤
│ GitHub   │ OSV.dev    │  Metrics     │  Suggestions          │
│ REST API │ Vuln API   │  Engine      │  Engine               │
│ GraphQL  │            │  (DORA)      │  (Heuristics)         │
├──────────┴────────────┴──────────────┴───────────────────────┤
│               Optional: Redis Cache (ioredis)                │
└──────────────────────────────────────────────────────────────┘

🛠 Tech Stack

🤝 Contributing

Contributions welcome! See CONTRIBUTING.md for dev setup, coding standards, and workflow.

git clone https://github.com/ParthibanRajasekaran/delivery-intel.git
cd delivery-intel
npm install
npm run validate   # lint + typecheck + test in one shot

📄 License

MIT. Use it however you want.