🏥 Organization Health Report - 2026-08-17

[github-actions[bot]]

🏥 Organization Health Report — github (2026-08-17)

Summary

Analysis of recent issue/PR activity across the github organization's public, non-archived repositories (241 repos discovered). Data collection note: the GitHub Search API returned inconsistent and heavily rate/scope-limited result sets during this run (total counts fluctuated between identical calls, and org-wide "open" queries returned as few as 7 issues / 2 PRs despite thousands of known open items across the org). Numbers below reflect the actual items retrieved and should be treated as a directional sample, not an exhaustive org-wide count.

📊 Volume Metrics (sampled)

Metric	Count
Issues opened (last 7d)	80
Issues closed (last 7d)	94
Issues opened (last 30d)	107
Issues closed (last 30d)	192
PRs opened (last 7d)	31
PRs closed (last 7d)	95
PRs opened (last 30d)	70
PRs closed (last 30d)	193

More issues/PRs were closed than opened in both windows — a healthy sign of throughput, though this sample is dominated by automation-heavy repos (e.g. gh-aw) that generate frequent bot-authored issues/PRs.

🏆 Top 5 Most Active Repositories (by sampled 30d activity)

Repository	Issues (30d)	PRs (30d)	Comments	Activity Score
gh-aw	78	11	76	227.0
rest-api-description	0	15	2	46.0
gh-aw-firewall	15	2	16	44.0
gh-aw-mcpg	7	1	3	18.5
copilot-sdk	2	4	4	18.0

gh-aw dominates activity, largely from automated agentic-workflow bookkeeping issues (daily reports, detection runs, no-op runs).

Top 10 Most Active Authors (sampled, bots excluded)

Author	Issues Opened	PRs Opened	Activity Score
github-openapi-bot	0	14	42
Copilot	0	9	27
lpcox	0	3	9
SamMorrowDrums	0	2	6
edburns	1	1	5
MackinnonBuck	0	1	3
manuelpuyol	0	1	3
mrecachinas	0	1	3
brianaj	0	1	3
pelikhan	1	0	2

🔥 High-Activity Unresolved Items (sampled, sorted by comment count)

Hot Issues

Issue	Repository	Comments	Age (days)	Link
#48858: [aw] Detection Runs	gh-aw	1541	18	View
#48838: [aw] No-Op Runs	gh-aw	1303	18	View
#6709: [aw] No-Op Runs	gh-aw-firewall	263	19	View
#143: [aw] No-Op Runs	gh-aw-actions	128	69	View
#9892: [aw] No-Op Runs	gh-aw-mcpg	121	25	View
#48884: [aw] agentic workflows out of sync	gh-aw	53	18	View
#223: "Copilot Requests" permission visibility for org-owned tokens	copilot-cli	31	314	View

Note: the top comment-count issues are automated tracking/bookkeeping issues (Detection Runs, No-Op Runs) used by agentic workflows themselves to log activity, not community discussion threads needing maintainer triage. The copilot-cli #223 permissions issue is a genuine long-lived (314 days) item worth revisiting.

Hot PRs

PR	Repository	Comments	Age (days)	Link
#172: Update translations via Co-op Translator	copilot-cli-for-beginners	22	53	View
#1163: Build current and next Go version	gh-ost	5	1466 (~4 years)	View

gh-ost PR #1163 has been open roughly 4 years — a candidate for closing or resolving.

⚠️ Items Needing Attention (from sampled open-issue set)

• Stale issues: 1 of 7 sampled open issues (30+ days old, no update in last 7 days)
• Stale PRs: 1 of 2 sampled open PRs
• Unassigned issues: 7 of 7 sampled open issues have no assignee
• Unlabeled issues: 0 of 7 sampled open issues are unlabeled

💡 Commentary and Recommendations

1. Automation-generated issues dominate visible activity. Repos like gh-aw, gh-aw-firewall, and gh-aw-mcpg produce very high comment volumes from self-reporting agentic workflows (daily reports, detection/no-op run trackers). These inflate "hot issue" rankings without representing user-facing problems — consider excluding token-usage-report/bookkeeping labels from future health dashboards to surface genuine community activity.
2. Long-lived open items exist. gh-ost Change web-search validation from error to warning for unsupported engines #1163 (~4 years old) and copilot-cli MCP Network Permissions Test Results - Domain Restrictions Validation #223 (314 days) are worth a maintainer pass — either close as stale or explicitly re-prioritize.
3. Assignee coverage is low in the sampled open-issue set (0/7 assigned) — consider a lightweight triage pass to assign owners to active issues so they don't go unaddressed.
4. Throughput looks healthy for the sampled data: closes outweigh opens for both issues and PRs in the last 7 and 30 days.

Full Data and Methodology

Data Collection

• Date generated: 2026-08-17
• Repositories discovered: 241 public, non-archived repos (via GraphQL, first page of 100 repos ordered by push date)
• Data source: GitHub REST Search API (search/issues) scoped to org:github
• Known limitation: the Search API in this environment returned inconsistent total_count values across identical repeated queries (e.g., open-issue counts of 0, 7, and 26 across separate calls), and org-wide "is:open" queries surfaced far fewer items than expected given the org's scale. All figures in this report reflect the literal item sets returned and should be treated as directional samples rather than exhaustive totals. A future run with authenticated elevated search access or per-repo enumeration (rather than org-wide search) is recommended for a fully accurate count.

Methodology

• Issues/PRs opened and closed in 7d/30d windows collected via time-filtered search queries with pagination
• Hot issues/PRs retrieved via sort=comments&order=desc
• Activity scores: issues*2 + prs*3 + comments*0.5 (repos), issues_opened*2 + prs_opened*3 (authors)
• Stale = created 30+ days ago AND not updated in the last 7 days
• 2-5 second delays inserted between paginated API calls to respect rate limits

Generated by 📊 Organization Health Report · auto · 64.1 AIC · ⌖ 11.7 AIC · ⊞ 14.3K · ◷

• expires on Aug 18, 2026, 12:37 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-08-18T08:37:57.066Z.

Closed by Workflow