Repository navigation
[detection-analysis] Detection Analysis Report — Partial 24h Window (2026-10-20) #70656
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #71243. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Warning
Coverage gap: roughly 19 of the requested 24 hours (2026-10-19T23:21Z–2026-10-20T18:26Z) were never downloaded due to a collection count limit, not an API rate limit (13,242/15,000 GitHub API calls remained at the end of collection). Findings below reflect only the ~4.9h window that was actually downloaded. Misconfiguration rule 1 ("gh-aw-detection: false on a workflow with >3 runs") is specified against a 7-day window in the task definition but was evaluated here against the available ~4.9h sample only — treat the flagged workflow as a lead to verify over the full 7 days, not a confirmed 7-day finding.
Comparison Chart
Regular runs (14) had a 21.4% success rate and averaged 7,507 tokens; detection-enabled runs (121) had an 86.0% success rate and averaged 173,121 tokens. The regular-run bucket is entirely smoke-test workflows (see table below), so the gap partly reflects sample composition (smoke tests vs. production workflows), not detection itself.
Misconfigured Workflows
No detection-job-level failures (rule 2) or alternating detection configuration within a single workflow (rule 3) were found in the observed sample: of 121 detection-enabled runs, 117 had a detection job in job_details (110 succeeded, 7 skipped, 0 failed); the remaining 4 had no detection job recorded.
View All Run Metrics
Per-workflow breakdown for the ~4.9h observed window (40 workflows, 135 classified runs):
28 additional runs in the window had only a GitHub run record downloaded (no aw_info.json/run_summary.json), so their detection status is unknown and they are excluded from the classification above (consistent with the "metadata-only groups remain unknown" rule).
View Historical Trend
10 of the last 30 days have recorded data points. Caveat: today's point reflects the same partial ~4.9h window described above, not a full day, so the sharp drop in both run counts on the latest date is a coverage artifact, not a real traffic decline — exclude it when judging day-over-day trend.
Recommendations
References:
All reactions