[lockfile-stats] Lockfile Statistics — 2026-08-30 #57236
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Lockfile Statistics Analysis Agent. A newer discussion is available at Discussion #57504. |
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.
Methodology: single-script compact JSON analysis (cached analyzer
lockfile_stats_v4.py, reused from prior runs; engine fromgh-aw-metadatacomment, permissions from theagentjob block, safe outputs fromGH_AW_SAFE_OUTPUTS_CONFIGenv JSON).Executive summary
engine_unknown=0,permissions_unknown=0,safe_outputs_config_missing=0,discussion_category_detected=92(==create_discussion_workflows=92),mcp_fallback_used_count=0.File size distribution
Trigger analysis
Top combinations:
schedule+workflow_dispatch(207),workflow_dispatchonly (38),pull_request+schedule+workflow_dispatch(29),pull_request+workflow_dispatch(9).Cron cadence: the dominant schedule is
0 0 */2 * *(every 2 days) at 42 workflows; the remaining ~198 scheduled workflows use distinct, staggered cron expressions (long tail, mostly count=1–3), suggesting deliberate desync to avoid a thundering-herd of scheduled runs.Safe outputs analysis
(Baseline safe-output scaffolding —
missing_data,missing_tool,noop,report_incomplete— present in 291/297 workflows.)Discussion categories (92
create_discussionworkflows, 100% resolved):Structural characteristics
Timeout distribution (step-level
timeout-minutes, includes multiple steps per file): 10min → 316, 45min → 297, 60min → 290, 90min → 3, 5min → 2, 120min → 2, 180min → 1, 15min → 1.Permission patterns (agent job)
The agent job is consistently read-only or none across all standard scopes — all mutation happens via the safe-outputs mechanism, not direct job permissions. Union-across-jobs permissions show every workflow (297/297) grants
writeto at least one scope somewhere in the job graph (e.g.issues: writeuniversally,contents: writein 204), reflecting the safe-output publishing jobs.Engine distribution
Top models:
openai/gpt-5.4(49),copilot/mai-code-1-flash-picker(44),copilot/claude-sonnet-4.5(12).Tool & MCP patterns
Most-used individual tools:
safeoutputs:missing_data/missing_tool/noop(291 each),safeoutputs:create_issue(145),github:get_commit/get_file_contents/etc. (118 each, GitHub read tool bundle).Interesting findings
safeoutputsMCP server and none show a direct write permission in the agent job — a clean, consistently-enforced separation between "agent reasoning" (read-only) and "side effects" (safe-output publishing jobs).create_discussioncategory assignment is 100% resolved (92/92) withauditsdominating (79/92, ~86%) — this very report belongs to that dominant category.0 0 */2 * *) repeats at scale (42×); the rest of the ~240 scheduled workflows use unique per-workflow offsets.Historical trends (vs. 2026-08-29)
Discussion category mix, safe-output type mix, and job/script averages were otherwise stable day-over-day — the engine reshuffle is the standout change.
Recommendations
discussions: readin the agent job but withcreate_discussionfurther down the pipeline confirms safe-outputs correctly isolates discussion writes; no permission-hardening action needed there.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