Repository navigation
[lockfile-stats] Lockfile Statistics — 2026-09-13 #60687
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Lockfile Statistics Analysis Agent. A newer discussion is available at Discussion #60922. |
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: 299 compiled
.lock.ymlworkflows, 46,367,016 bytes total (~44.2 MB), avg 155.1 KB, min 91.6 KB, max 248.1 KB. 0 malformed/skipped files.File size distribution
Trigger analysis
Top trigger combinations:
schedule+workflow_dispatch(209),workflow_dispatchonly (38),pull_request+schedule+workflow_dispatch(29),pull_request+workflow_dispatch(9).Cron frequencies:
0 0 */2 * *(every 2 days) is the single largest cluster at 42 workflows; the remaining ~30 distinct cron strings are mostly unique per-workflow minute/hour offsets — a jitter pattern to avoid runner stampedes.Safe outputs analysis
Near-universal scaffolding:
noop,missing_tool,missing_data,report_incompleteeach appear in 293/299 workflows (98%). Beyond that:create_issue146 (49%),create_discussion92 (31%),add_comment77 (26%),create_pull_request64 (21%),push_repo_memory36,add_labels32,upload_asset26,mentions23, then a long tail down to single-use types (e.g.jira_create_issue,linear_create_issue,update_project).Discussion categories (92
create_discussionworkflows, all 92 resolved — 0 unresolved):Structural characteristics
Permission patterns
Agent job (primary per-workflow scope, mirrors frontmatter
permissions:):Union across all jobs (a scope counts write if any job grants it): all 299 workflows grant at least one write scope. Notably
issuesis write in all 299 (100%) at the union level despite the agent job itself often being read/none — some other job (safe-outputs handler) carries that write grant.contentswrite 206 / read 93;pull-requestswrite 146 / read 116 / none 37;discussionswrite 96 / read 10 / none 193.permissions_unknown: 0 (fully resolved for every lockfile).Engine distribution
engine_unknown: 0 (resolved viagh-aw-metadataagent_idfor every lockfile).Tool & MCP patterns
MCP servers by workflow count:
safeoutputs299 (100%, always present),github175 (59%),agenticworkflows44,serena25,mcpscripts12,tavily5,sentry3, remainder (ast-grep,datadog,deepwiki,microsoftdocs,grafana,kreuzberg,mempalace,graft,agentdb,ruflo) 1–2 each. No fallback (comment-scraping) parsing was needed — 100% resolved via thegh-aw-manifestJSON.Timeout distribution (minutes, across job step declarations): 10min ×318, 45min ×299, 60min ×292, then rare 90/5/120/180/15.
Interesting findings
issues: write(299/299), even though many agent jobs themselves only holdissues: readornone— the write grant is carried by a downstream job (safe-outputs handler), not the agent step itself.auditsis the overwhelming default discussion category (79/92, 86%) forcreate_discussionworkflows — this very report follows that convention.Historical trends (vs. 2026-09-12)
Engine, permission, MCP, safe-output-type, and discussion-category distributions were unchanged day-over-day except a minor model-string shift (
copilot/gpt-5.3-codex34→33). Overall: a quiet day of incremental workflow growth with no structural or engine-mix shifts.Recommendations
issues: writeat the union level, but only 146/299 (49%) actually usecreate_issue/update_issue/etc. Consider auditing whether the safe-outputs job'sissues: writegrant can be scoped down for workflows that never emit issue-related safe outputs.0 0 */2 * *cron to confirm minute/hour offsets are still deliberately staggered, since they share the same day-cadence.auditscovers 86% of discussion-producing workflows; confirm this default isn't masking missingcategoryconfiguration for workflows that intend a different category.Methodology: single-script compact JSON analysis.
References:
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