🏥 Organization Health Report — 2026-05-04

[github-actions[bot]]

The github organization is active and productive. Over the last 7 days, 83 issues and 80 pull requests were opened, reflecting strong contributor engagement. The gh-aw and gh-aw-firewall repositories dominate activity, driven largely by automated workflows and AI-assisted contributions. The overall PR merge velocity is high (92 PRs closed in 7 days), indicating efficient review cycles.

---

📊 Volume Metrics

Overall Status

Metric	Count
Total Open Issues	60
Total Open PRs	51
Stale Issues (open 30+ days)	7
Stale PRs (open 30+ days)	48

Recent Activity (Last 7 Days)

Metric	Count
Issues Opened	83
Issues Closed	93
PRs Opened	80
PRs Closed	92

✅ Healthy signal: More issues and PRs are being closed than opened — the org is keeping up with its backlog.

Recent Activity (Last 30 Days)

Metric	Count
Issues Opened	83
Issues Closed	93
PRs Opened	80
PRs Closed	92

i️ The 7-day and 30-day windows are identical, indicating that nearly all activity occurred within the last week.

---

🏆 Top 5 Most Active Repositories

Repository	Issues (30d)	PRs (30d)	Comments	Activity Score
gh-aw	41	64	150	406
gh-aw-firewall	22	3	55	80
gh-aw-mcpg	20	2	14	53
codeql-variant-analysis-action	0	2	0	6
dependabot-action	0	2	0	6

gh-aw is by far the most active repository, accounting for ~50% of all issues and ~80% of PRs in the organization — likely driven by the AI agentic workflow system itself.

---

🤖 Top 10 Most Active Authors

View Top Contributors

Author	Issues Opened	PRs Opened	Activity Score
github-actions[bot]	81	22	125
Copilot	0	48	96
dependabot[bot]	0	6	12
lpcox	1	1	3
codeql-ci	0	1	2

Note: The top "contributors" are bots — github-actions[bot] (automated issue creation from workflows) and Copilot (AI-assisted PRs). This is expected for an agentic workflow organization.

---

🔥 High-Activity Items Needing Attention

Hot Issues (Most Discussed)

Issue	Repository	Comments	Created	Link
#29134: [aw] No-Op Runs	gh-aw	625	2025-03-12	View
#1630: [agentics] No-Op Runs	gh-aw-firewall	146	2025-08-15	View
#2301: [aw] No-Op Runs	gh-aw-firewall	85	2025-11-20	View

⚠️ Note: Issues about "No-Op Runs" appear across multiple repositories with very high comment counts. These may represent long-running operational tracking issues that warrant review.

Hot PRs (Most Discussed)

PR	Repository	Comments	Link
#29626: feat: add edit-wiki safe-output	gh-aw	58	View
#1164: Add Rust SDK (technical preview)	copilot-sdk	32	View
#1163: Build current and next Go version	gh-ost	5	View

---

⚠️ Items Needing Attention

Category	Count	Notes
Stale Issues (open 30+ days)	7	Low — good health signal
Stale PRs (open 30+ days)	48	⚠️ High — needs triage
Open Issues Without Assignees	45 / 60	75% unassigned
Open Issues Without Labels	4 / 60	Well-labeled overall

Stale PRs (48 open for 30+ days) is the most concerning metric. Many of these may be in gh-aw given its dominance. Maintainers should review and either merge, close, or add context to these PRs.

---

💡 Commentary and Recommendations

1. Triage stale PRs: 48 PRs open for 30+ days is a significant backlog. A dedicated triage session for gh-aw (the most active repo) would clear most of these.

2. Assign open issues: 75% of open issues have no assignee. Even lightweight assignment helps ensure issues don't fall through the cracks.

3. Monitor "No-Op Runs" issues: The high-comment tracking issues ([aw] No-Op Runs #29134, Cleanup: Remove workflow cancellation API calls from compiler #1630, [smoke-detector] 🔁 Smoke Test Investigation - Smoke Copilot Run #18786022255: Permission Denied Recurrence #2301) may warrant being closed and replaced with fresh issues or a dashboard to avoid comment bloat.

4. Bot vs. human ratio: The top contributors are bots. This is a feature of an agentic workflow org, but human review and oversight of bot-generated issues/PRs should be ensured.

5. Activity concentration: ~50% of all activity is in gh-aw. Spreading context to other repos (e.g., gh-aw-firewall, gh-aw-mcpg) may help distribute the review load.

---

📋 Methodology and Data Sources

Data Collection

• Report Date: 2026-05-04
• Repositories Analyzed: 100 public, non-archived repositories (top 100 by recent update)
• API: GitHub Search API via gh CLI
• Analysis Tool: Python + jq for aggregation

Metrics

• All counts reflect GitHub Search API totals
• Activity Score = issues × 2 + PRs × 3 + comments × 0.5
• "Stale" = open for 30+ days
• Data collected with rate-limit delays between API calls

Limitations

• GitHub Search API returns up to 1,000 results per query; org-wide totals are used for precision
• The 7-day and 30-day windows show identical results, suggesting all recent activity burst occurred in the last week
• Bot accounts (github-actions[bot], Copilot, dependabot[bot]) are included in author counts

References:

• §25310376162

Generated by Organization Health Report · ● 917.9K · ◷

• expires on May 5, 2026, 9:10 AM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-05-05T09:10:38.010Z.

Closed by Workflow