[detection-analysis] Detection Analysis Report — 2026-09-01 #57793
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #58051. |
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
gh-aw-detection: false): 0 (0%)Note
Every run in this window had threat detection active — either explicitly (
gh-aw-detection: true, 225 runs) or via the default (feature key absent, 28 runs). No workflow opted out of detection, and no detection job showed a failing conclusion, so there is nothing to flag this cycle.Comparison Chart
Because there were zero opted-out ("Regular") runs, that bar is flat at 0 across every metric — the chart mainly documents full adoption of the detection default rather than a real head-to-head comparison this cycle.
Misconfigured Workflows
No misconfigured workflows detected in this window. All three rules (detection disabled on an active workflow, detection job itself failing, or flapping between enabled/disabled) returned zero matches.
View All Run Metrics
105 distinct workflows ran in the window. Full per-workflow breakdown (all detection-enabled; sorted by run count):
The remaining 87 workflows each had exactly 1 run in the window (mix of successes and failures unrelated to detection configuration — e.g.
Daily Cache Strategy Analyzer,Terminal Stylist, andWorkflow Normalizereach burned 1M+ tokens on their single run).View Historical Trend
3 data points now recorded (2026-08-23, 2026-08-24, 2026-09-01). Regular-run success rate and count have been 0 across the last two snapshots — no workflow in this repository has opted out of detection recently.
Recommendations
aw_info.json/run_summary.json) is worth a separate look if it recurs: confirm whether those 135 runs are genuinely still in-progress at collection time or whether log collection is silently dropping some runs.Daily Fact,Daily Storify,Functional Pragmatist,PureLock) with 0 tokens used, suggesting early setup/permission failures rather than detection-related issues; worth triaging separately from this detection-specific report.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions