🏥 Organization Health Report — 2026-08-31

[github-actions[bot]]

github org, public non-archived repos — activity is heavily concentrated in gh-aw and its satellite repos (gh-aw-mcpg, gh-aw-firewall), driven almost entirely by automated agentic workflows (github-actions[bot], Copilot, dependabot[bot]) rather than direct human authorship.

📊 Volume Metrics

Overall Status (org:github, public repos, current snapshot)

Metric	Count
Total Open Issues	9
Total Closed Issues	97
Total Open PRs	25
Total Closed PRs	91

Recent Activity (created in last 30 days, sampled via search)

Metric	Count
Issues Opened	88
Issues Closed	24
PRs Opened	66
PRs Closed	51

Note: within this 30-day cohort, all 88 sampled issues and all 66 sampled PRs were also created in the trailing 7 days — indicating this is a burst of very recent, high-velocity activity rather than a steady month-long trickle.

🏆 Top 5 Most Active Repositories (last 30 days)

Repository	Recent Issues	Recent PRs	Comments	Activity Score
gh-aw	63	38	191	335.5
gh-aw-mcpg	19	8	34	79.0
gh-aw-firewall	3	6	69	58.5
gh-aw-threat-detection	3	0	2	7.0
dependabot-action	0	2	0	6.0

gh-aw dominates activity by a wide margin — it's the primary development surface, generating most of the issues (largely automated agent run trackers) and PRs. gh-aw-firewall has an outsized comment count relative to its issue/PR volume, suggesting active discussion on a small number of items (worth checking for contentious or complex PRs).

Top 10 Most Active Authors

Author	Issues Opened	PRs Opened	Activity Score
github-actions[bot]	88	23	245
Copilot	0	32	96
dependabot[bot]	0	10	30
csmlo	0	1	3

Only 4 distinct authors appear in the 30-day sample; nearly all activity is bot/agent-driven (automated workflow run trackers, Copilot-authored PRs, Dependabot updates). Human-authored activity (csmlo) is minimal in this window.

🔥 High-Activity Unresolved Items

Hot Issues (Need Attention)

Issue	Repository	Comments	Link
#57332: Issue Monster failed to assign agent	gh-aw	8	#57332
#57378: Enrich schema descriptions for redirect/tracker-id	gh-aw	3	#57378
#57373: Add test coverage to compiler_safe_outputs_builder.go	gh-aw	3	#57373
#57365: VulnHunter findings in github/gh-aw	gh-aw	3	#57365
#57362: Multi-Device Docs Testing Report	gh-aw	2	#57362
#57335: PR Description Updater reported incomplete result	gh-aw	2	#57335
#12205: No-Op Runs	gh-aw-mcpg	2	github/gh-aw-mcpg#12205

No open PRs surfaced with notable comment counts in this sample — recent PRs are being merged/closed quickly (51 of 66 opened in the window are already closed).

⚠️ Items Needing Attention

• Stale Issues (open 30+ days, no update in 7+ days): 1
• Stale PRs (open 30+ days, no update in 7+ days): 10
• Unassigned Issues: 9 of 9 currently-open issues have no assignee
• Unlabeled Issues: 1 of 9 currently-open issues has no labels

The 10 stale open PRs are the most actionable item here — worth a manual sweep to close, rebase, or merge them since PR throughput is otherwise very high (91 closed vs 25 open).

💡 Commentary and Recommendations

1. This is a highly automated repo ecosystem. Nearly all issue/PR creation in the last 30 days comes from bots and agentic workflows (github-actions[bot], Copilot, dependabot[bot]). Human-authored issues/PRs are rare in this sample — consider whether automated issue trackers that auto-close on success are cluttering signal for genuine problems.
2. Unassigned open issues (9/9) — while volume is low, triage ownership isn't visible. Even lightweight auto-assignment or a "needs triage" label pass would help.
3. 10 stale open PRs stand out against a otherwise fast merge cadence (91 closed/30d) — these are likely blocked, abandoned, or low-priority; a quick review/close pass is recommended.
4. gh-aw-firewall's comment-heavy but PR/issue-light profile suggests concentrated discussion — worth spot-checking whether decisions there are being tracked/resolved.

Full Data and Methodology

Data Collection

• Date Range: last 7 and 30 days relative to 2026-08-31
• Repositories Analyzed: 50 public, non-archived repositories discovered via gh api search/repositories
• Issues Analyzed: 88 (30-day creation window sample, single-page GitHub Search API result)
• PRs Analyzed: 66 (30-day creation window sample, single-page GitHub Search API result)
• Current open/closed totals: queried directly via is:open/is:closed search counts

Methodology

• Data collected using gh api search/issues and gh api search/repositories (GitHub Search API), no MCP server available in this run.
• GitHub Search API results are capped at 100 items per query; the 30-day creation-window queries for org:github returned complete result sets (88 and 66 items respectively, both under the 100-item cap), so no sampling bias from pagination was introduced.
• Analyzed using plain Python (pandas installation was unavailable in time; equivalent logic implemented natively).
• Activity scores: issues*2 + prs*3 + comments*0.5 (repos), issues*2 + prs*3 (authors).
• Delays of 3–5 seconds were added between GitHub Search API calls to respect rate limits; a few initial calls returned transiently incorrect low counts (likely search index eventual-consistency) and were retried successfully.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by 📊 Organization Health Report · copilot · auto · 59.3 AIC · ⌖ 10.4 AIC · ⊞ 13.1K · ◷

• expires on Sep 1, 2026, 12:49 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-09-01T08:49:42.818Z.

Closed by Workflow