[lockfile-stats] Lockfile Statistics — 2026-09-14 #60922
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-09-15T20:29:04.630Z.
|
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.
Analysis of
.github/workflows/*.lock.ymlingithub/gh-aw— 299 compiled lockfiles, 46,336,082 bytes total (avg 154,970 B, min 91,533 B, max 247,974 B). 0 malformed/skipped files.File size distribution
Trigger analysis
Top triggers:
workflow_dispatch(291),schedule(242),pull_request(43),issues(5),issue_comment/workflow_call(3 each).Most common combinations:
schedule+workflow_dispatch(209),workflow_dispatchonly (38),pull_request+schedule+workflow_dispatch(29),pull_request+workflow_dispatch(9).Cron cadence: 42 workflows share
0 0 */2 * *(every 2 days); the remainder are mostly unique daily/weekly schedules.Safe outputs analysis
create_issue: 146,create_discussion: 92,add_comment: 77,create_pull_request: 64,push_repo_memory: 36,add_labels: 32audits(79),announcements(5),artifacts/dev/research(2 each),general/daily-news(1 each)Structural characteristics
Timeout distribution (job-level, minutes): 10min appears 318×, 45min 299×, 60min 292× — most workflows layer multiple timeout tiers across jobs.
Permission patterns (agent job)
contents: readis universal (299/299).issues/pull-requestsread access ~260/255 workflows;actions: readin 114;discussions: readin 52 (tracks with the 92 discussion-producers, since some also write via a separate reporting job). Only 2 workflows grantid-token: writeat the agent-job level.Unioned across all jobs (agent + write-back jobs), 299/299 workflows grant at least one write scope somewhere in the workflow — expected, since safe-output write-back jobs run with elevated, scoped permissions separate from the read-only agent job.
Engine distribution
0 unresolved (
engine_unknown).Tool & MCP patterns
MCP servers by workflow count:
safeoutputs(299, universal),github(175),agenticworkflows(44),serena(25),mcpscripts(12), plus long tail (tavily, sentry, ast-grep, datadog, deepwiki, microsoftdocs, grafana, kreuzberg, mempalace, graft, agentdb, ruflo).Most-used individual tools:
safeoutputs:missing_data/missing_tool/noop(293 each — near-universal safety scaffolding),github:get_commit/get_file_contents(167),safeoutputs:create_issue(146),github:get_me(143).Interesting findings
missing_data/missing_tool/noopsafe-output triad — this has become a de facto standard scaffold, not an occasional pattern.copilotis now the plurality engine (123/299, 41%) ahead ofcodex(74) andclaude(56) — a notable shift toward Copilot-backed agentic workflows in this repo.GH_AW_SAFE_OUTPUTS_CONFIG— no fallback regex parsing was needed, indicating consistent lockfile compilation.id-token: write(OIDC) appears in only 2/299 workflows at the agent-job level, suggesting minimal reliance on OIDC-based cloud auth across the fleet.Historical trends (vs. 2026-09-13)
No structural shifts day-over-day; the byte-count dip reflects minor lockfile regeneration/formatting, not new workflows.
Recommendations
missing_data/missing_tool/noop/report_incompletescaffold into a shared compiled fragment if not already, given its near-100% adoption.copilotnow the plurality engine, ensure engine-specific documentation/tooling parity keeps pace withclaude/codex.Methodology: single-script compact JSON analysis (
lockfile_stats_v4.py, cached in/tmp/gh-aw/cache-memory/scripts/).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