Generated: 2026-07-23 03:24 UTC

Whether each scanner is on pace to complete its target cycle (30 days for most scanners, 60 days for Lighthouse and Relationships), based on distinct URLs scanned in the last 7 days projected forward against the full eligible corpus. See WORKFLOW_ORCHESTRATION_AUDIT.md Section 11 for the methodology.

Scanner Target cycle Eligible URLs Scanned (window) Daily throughput Projected cycle Status
accessibility 30d 87,696 13,296 (last 7d) 1,899.4/day 46.2d 🔴 Behind
social_media 30d 87,696 49,498 (last 7d) 7,071.1/day 12.4d 🟢 Ahead
technology 30d 87,696 4,068 (last 7d) 581.1/day 150.9d 🔴 Behind
third_party_js 30d 87,696 14,387 (last 7d) 2,055.3/day 42.7d 🔴 Behind
overlays 30d 87,696 0 (last 7d) 0.0/day —d ⚪ No data
lighthouse 60d 87,696 3,746 (last 7d) 535.1/day 163.9d 🔴 Behind

Projection method: effective daily throughput = distinct URLs scanned in the last 7 days ÷ 7; projected cycle days = eligible URLs ÷ effective daily throughput. The 7-day measurement window reflects recent scan velocity and is independent of each scanner’s own target cycle length – see src/services/cycle_pace_tracker.py’s module docstring for why. ‘No data’ means the scanner has no rows in its metadata.db within the window (never run against this database, or the database doesn’t cover this scanner).