[lockfile-stats] Lockfile Statistics Audit — 2026-07-20 #46921
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Lockfile Statistics Analysis Agent. A newer discussion is available at Discussion #47139. |
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.
Executive Summary
Analysis of 260
.github/workflows/*.lock.ymlfiles on 2026-07-20 (0 malformed/skipped).yaml.safe_load(available)File Size Distribution
Largest:
smoke-copilot(202 KB),smoke-copilot-aoai-entra(186 KB),smoke-claude(180 KB). Smallest:example-permissions-warning(80 KB),firewall(81 KB). The near-uniform 100–250 KB band reflects the shared compiled runtime boilerplate every lockfile carries.Trigger Analysis
Top combinations:
schedule+workflow_dispatch(174),workflow_dispatchalone (47),pull_request+workflow_dispatch(26). Nearly every workflow (253/260) exposes manual dispatch; 178 run on cron. Cron cadence skews to daily* * *and weekday1-5windows, with a handful of*/6/*/4/*/12high-frequency schedules.Safe Outputs Analysis
Baseline safety tools (
report-incomplete,missing-data,missing-tool,noop) appear in 255/260 lockfiles. Beyond baseline, the active write surface:Discussion categories:
audits(77),announcements(5),artifacts(2),dev(2),daily-news(1),research(1) — the audit corpus dominates discussion output.Structural Characteristics
release)smoke-copilot)Scripts (run steps) total 14,777 (~57/workflow). The 79-step floor confirms a heavy fixed compilation scaffold shared across all lockfiles.
Permission Patterns
Read (top):
actions260,contents260,pull-requests226,issues222,discussions50,security-events14.Write (top):
issues253,contents174,pull-requests123,discussions93,copilot-requests67,checks13.Universal
actions+contentsread is expected. Write-issues on 253/260 is broad; contents-write on 174 warrants periodic least-privilege review.Tool & MCP Patterns
Engines: copilot 64, claude 63, codex 15, gemini/antigravity/opencode 1 each; 115 unresolved ("other") — see findings.
Timeouts
31–60 minon all 260 jobs (default runtime cap);6–15 minon 28 jobs,<=5 minon 2.Interesting Findings
otherunder regex fallback despite YAML being available. Named engines (copilot/claude/codex) only cover 143; the analyzer's engine heuristic under-classifies nearly half the corpus and should read the compiled engine field directly.auditscategory; this reporting agent is part of a large self-observability fleet.push-repo-memory(36) +comment-memory(5) show ~16% of workflows now persist cross-run state.workflow_dispatch, making the fleet almost entirely operator-triggerable on demand.Historical Trends (vs 2026-07-19)
Steady daily growth: +2 workflows added ~1.4 MB and ~1,900 steps, consistent with new Claude-engine issue-creating agents.
Recommendations
otherbucket in future audits.contents: write; confirm each genuinely commits or pushes.Methodology
Single-script compact JSON analysis: one cached Python analyzer (
lockfile_stats_v1.py,yaml.safe_loadprimary with regex fallback for safe-output/permission/category fields) parsed all 260 lockfiles in one pass, emitting a ~7 KB summary; the report reasons only from that JSON. 0 lockfiles skipped.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
All reactions