[detection-analysis] Detection Analysis Report — 2026-08-02 #49869
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #50116. |
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
2026-08-02T17:33:41Z→2026-08-02T23:15:08Z(~5.7h) given this repo's high run volumeWarning
1 misconfigured workflow detected: a monitoring-role workflow is missing
gh-aw-detection: true.Comparison Chart
Detection-enabled runs had a higher success rate (88.76% vs 81.82%) but over 2x the average token usage (55,068 vs 26,522) — expected overhead from the added threat-detection job.
Misconfigured Workflows
gh-aw-detectionis not enabledgh-aw-detection: trueto.github/workflows/daily-regulatory.mdfrontmatter — this workflow's own description says it "monitors and cross-checks other daily report agents' outputs for data consistency and anomalies," matching the audit/monitor pattern.Note:
Daily Agentic Workflow AIC Usage Audit(.github/workflows/agentic-token-audit.md) was excluded from this check per the documented repository-level opt-out (source-managed fromgithubnext/agentic-ops).View All Run Metrics
View Historical Trend
30-day history now has 30 recorded entries (23 within the trailing 30-day window). Detection-enabled adoption has grown sharply, overtaking regular runs on 2026-07-30 and again in today's window (89 vs 11).
Recommendations
gh-aw-detection: trueto.github/workflows/daily-regulatory.md— its own description matches the monitoring/audit pattern this repo requires detection for.All reactions