[lockfile-stats] Lockfile Statistics Audit — 2026-06-06 (242 lockfiles, 24.6 MB) #37397
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Lockfile Statistics Analysis Agent. A newer discussion is available at Discussion #37650. |
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.
-
Executive Summary
Snapshot of 242 compiled lockfiles (
.github/workflows/*.lock.yml) on 2026-06-06. Zero malformed/skipped files.test-workflow) / 162.9 KB (smoke-copilot-aoai-apikey)copilot(159)github(6,656 refs)Compiled workflows are uniformly large (generated YAML); every file falls between 67–163 KB.
File Size Distribution
Largest & smallest lockfiles
Largest:
smoke-copilot-aoai-apikey(162.9 KB),smoke-copilot(162.2 KB),smoke-claude(158.4 KB),smoke-copilot-arm(150.8 KB),smoke-codex(137.7 KB),mcp-inspector,issue-monster,deep-report,cloclo,daily-news.Smallest:
test-workflow(67.1 KB),example-permissions-warning(67.8 KB),codex-github-remote-mcp-test(67.8 KB),firewall(69.0 KB),ace-editor(76.2 KB).Trigger Analysis
workflow_dispatchschedulepull_requestissuesissue_commentpushworkflow_run/discussion/discussion_comment/pull_request_review_commentTop combinations:
schedule+workflow_dispatch(159),workflow_dispatchonly (45),pull_request+workflow_dispatch(26). The corpus is overwhelmingly scheduled-agent oriented: 163 workflows run on cron, nearly all also manually dispatchable.Cron cadence notes
Schedules are well-jittered (off-minute, staggered hours) — almost no two share a minute mark. Common shapes: daily (
* * *), weekday (* * 1-5), every-6h (*/6), every-4h (*/4), weekly. This reflects good scheduling hygiene to avoid fleet-wide API spikes.Safe Outputs Analysis
Structural Characteristics
firewall-escape)smoke-copilot)Totals: 1,941 jobs, 25,913 steps, 12,308 embedded scripts across the corpus.
Permission Patterns
The analyzer reports a uniform
{}top-level permission kind for all 242 files (read/write maps empty). Like safe-outputs, granular permission extraction is av1parser gap rather than a finding that workflows lack permissions.Tool & MCP Patterns
githubplaywrightsentryruflografanaarxiv/deepwikiGitHub MCP is the near-universal backbone. The most-referenced GitHub tools (128 workflows each) are read APIs:
issue_read,get_file_contents,list_commits,get_pull_request,list_dependabot_alerts,get_code_scanning_alert, etc. — consistent with the read-only MCP posture.Engine distribution
Interesting Findings
antigravity,crush,gemini,opencode,pi), signalling active engine experimentation.smoke-*workflows (137–163 KB), each exercising a full engine+MCP matrix.Historical Trends
Day-over-day (2026-06-05 → 2026-06-06)
workflow_dispatchscheduleSince baseline (2026-05-20, ~17 days)
Steady organic growth: +9 workflows and ~11% larger average compiled output, reflecting both new agents and a heavier generated runtime.
Recommendations
lockfile_stats_v2analyzer that parses safe-output types, discussion categories, and granular permissions from the current lock format (extract from the embeddedGITHUB_AW_SAFE_OUTPUTSJSON and the per-jobpermissions:blocks). Today's empties for these three sections are parser gaps, not real zeros..lock.ymldiffs reviewable.Methodology note: single-script compact JSON analysis — all 242 lockfiles parsed once by a cached analyzer (
lockfile_stats_v1.py) into a ≤5 KB JSON summary; the report is derived solely from that summary and prior-day history snapshots. No individual lockfile was opened for analysis.Beta Was this translation helpful? Give feedback.
All reactions