[detection-analysis] Detection Analysis Report — 2026-07-05 (last 24h) #43550
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #43797. |
Beta Was this translation helpful? Give feedback.
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
3 workflows were flagged as misconfigured for the detection feature. See the table below for recommended fixes.
Detection-enabled runs showed a higher success rate (92.3% vs 81.3%) but higher average token usage (~1.01M vs ~705K), consistent with the extra detection job stage. All 26 detection runs had a passing detection job.
Comparison Chart
Misconfigured Workflows
gh-aw-detection: false, 4 runs)Smoke CIis a high-frequency CI job with 0 token usage, so disabling detection is likely deliberate — document the exemption or enable detection. Example run: 28735256896gh-aw-detection: truegh-aw-detection: true— analysis workflows that process agent prompts/output should run threat detection. Example run: 28737657305gh-aw-detection: truegh-aw-detection: true— report-generation workflows should run threat detection. Example run: 28741234846View All Run Metrics (35 workflows)
View Historical Trend
Trend built from 9 days of cached daily metrics (
detection-metrics/history.jsonl). Detection-run success rate has stayed in the ~80–95% band while daily detection-run volume trends gently upward.Recommendations
Copilot Agent Prompt Clustering AnalysisandGitHub MCP Remote Server Tools Report Generatorboth process agent-generated content and should run threat detection (gh-aw-detection: true).Smoke CIopt-out — it explicitly setsgh-aw-detection: falseacross all 4 in-window runs. If detection is intentionally skipped for this CI smoke test, record the exemption; its 0% success / 0-token runs may also warrant a separate look.PR Code Quality Reviewerfailure rate (36% success over 11 runs) — unrelated to detection but the largest reliability gap in the window.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions