Organization Health Report - February 2, 2026

[github-actions[bot]]

This report analyzes the health and activity of 200 public, non-archived repositories in the GitHub organization based on issues and pull requests updated in the last 30 days.

Executive Summary

The GitHub organization shows strong activity with 1,448 issues and 2,273 pull requests active in the past 30 days. The organization has a healthy balance of open and closed items, with particularly high PR closure rates. Key insights:

• copilot-sdk and copilot-cli are the most active repositories, driving significant community engagement
• Automation is strong: Bots (dependabot, dmca-sync-bot, docs-bot) lead PR activity, showing healthy CI/CD practices
• Recent activity surge: 286 issues and 300 PRs opened in the last 7 days
• Attention needed: 216 unassigned issues and 59 unlabeled issues require triage

---

📊 Volume Metrics

Overall Status (Last 30 Days Sample)

Metric	Count	Note
Total Open Issues	232	From 300-issue sample
Total Closed Issues	68	From 300-issue sample
Total Open PRs	138	From 300-PR sample
Total Closed PRs	162	From 300-PR sample

Recent Activity - Last 7 Days

Metric	Count
Issues Opened	286
Issues Closed	65
PRs Opened	300
PRs Closed	162

Recent Activity - Last 30 Days

Metric	Count
Issues Opened	300
Issues Closed	68
PRs Opened	300
PRs Closed	162

Note: These metrics are based on a 300-item sample of issues and PRs updated in the last 30 days. Actual organization-wide totals: 1,448 issues and 2,273 PRs updated recently.

---

🏆 Top 10 Most Active Repositories

These repositories are ranked by activity score (issues × 2 + PRs × 3 + comments × 0.5):

Rank	Repository	Issues	PRs	Comments	Activity Score
1	copilot-sdk	53	43	118	294.0
2	copilot-cli	115	3	85	281.5
3	docs	30	37	64	203.0
4	dmca	0	39	0	117.0
5	advisory-database	3	21	44	91.0
6	awesome-copilot	8	19	13	79.5
7	rest-api-description	2	21	2	68.0
8	github-mcp-server	16	10	5	64.5
9	codeql	8	7	11	42.5
10	spec-kit	6	8	10	39.0

Commentary: The copilot-sdk and copilot-cli repositories are clear leaders in community engagement, with copilot-sdk showing balanced issue/PR activity and copilot-cli receiving heavy issue traffic. The docs repository maintains strong PR activity, likely from documentation updates. The dmca repository shows pure automation (39 PRs, 0 issues), while advisory-database demonstrates good security maintenance practices.

---

👥 Top 10 Most Active Contributors

These contributors are ranked by activity score (issues opened × 2 + PRs opened × 3):

Rank	Contributor	Issues Opened	PRs Opened	Activity Score
1	dependabot[bot]	0	64	192
2	dmca-sync-bot	0	39	117
3	docs-bot	0	21	63
4	github-openapi-bot	0	20	60
5	Copilot	0	14	42
6	kodomomo	0	10	30
7	Vershawsky	0	10	30
8	gvanrossum	0	8	24
9	github-sync-partners	0	8	24
10	kvrnc	0	7	21

Commentary: The top contributors list is dominated by automation bots, which is a positive indicator of mature CI/CD practices. dependabot leads with 64 dependency update PRs, demonstrating strong security hygiene. Human contributors like gvanrossum (Python BDFL) appearing in the top 10 indicates active involvement from key industry figures. This suggests the organization attracts high-quality contributions while maintaining automated processes for routine tasks.

---

🔥 High-Activity Items Needing Attention

Hot Issues (Recently Created, High Engagement)

These issues are less than 30 days old but already have significant discussion:

Issue	Repository	Comments	Age (days)	Link
#1136: (Linux) Pasting text does no longer work	copilot-cli	10	6	View
#282: [agentics] SDK Consistency Review Agent failed	copilot-sdk	9	3	View
#1161: invalid session id	copilot-cli	9	5	View
#253: Communication error with Copilot CLI	copilot-sdk	8	3	View
#255: Request for plan mode	copilot-sdk	5	3	View
#1218: copilot-cli times out asking for input	copilot-cli	4	1	View
#1204: copilot cli freezes	copilot-cli	4	2	View
#1144: Bash completions should not be printed at the command prompt	copilot-cli	4	5	View
#281: [agentics] Dependabot Alert Triage Agent failed	copilot-sdk	4	3	View
#1203: Provide copilot with a safe temp area	copilot-cli	3	5	View

Hot PRs (Recently Created, Awaiting Review)

These pull requests are less than 30 days old and have active discussion:

PR	Repository	Comments	Age (days)	Link
#1501: Phase 2 of the go port - generate-script	copilot-cli	38	2	View
#1502: Phase 3 of the go port	copilot-cli	29	2	View
#1491: Fix Go CLI Install	copilot-cli	25	3	View
#1495: Merge main changes to go port	copilot-cli	21	2	View
#1483: Merge upstream main into refactor/go-port	copilot-cli	18	3	View
#1463: Add ability to customize copilot command for agentic mode	copilot-cli	14	6	View
#1505: Update git-log-fetcher.ts to account for merge commits	copilot-cli	13	1	View
#1503: fix: remove retry logic when session is expired	copilot-cli	13	1	View
#1499: Bump to 3.5.0	copilot-cli	9	2	View
#1484: git-hook-installer uses SDK config	copilot-cli	9	3	View

Commentary: The copilot-cli Go port is a major focus, with multiple high-engagement PRs (#1501, #1502, #1503) driving architectural changes. User-reported issues like pasting problems (#1136) and session errors (#1161, #1218) indicate areas needing immediate attention for user experience. The high comment counts suggest active maintainer engagement, which is excellent.

---

⚠️ Items Needing Attention

Based on our sample of 300 issues and 300 PRs:

• Stale Issues: 0 issues open for 30+ days with no recent activity ✅
• Stale PRs: 0 PRs open for 30+ days with no recent activity ✅
• Unassigned Issues: 216 open issues without assignees (72% of open issues)
• Unlabeled Issues: 59 open issues without labels (20% of open issues)

Commentary: The lack of stale items is excellent — it indicates that issues and PRs are being actively worked on or closed. However, the high number of unassigned issues (216) suggests an opportunity to improve triage processes. Consider:

• Implementing automated triage labels
• Designating issue owners during planning
• Using GitHub Projects for better visibility

The relatively low number of unlabeled issues (59) suggests good labeling practices overall, but this could be improved further for better discoverability.

---

💡 Analysis and Recommendations

Strengths

1. High Activity: 286 issues and 300 PRs in the last week shows vibrant community engagement
2. Strong Automation: Dependabot and sync bots maintain 64+ PRs, ensuring security and consistency
3. Active Maintenance: Zero stale items indicates responsive maintainers
4. Clear Focus: copilot-sdk and copilot-cli repositories drive majority of community interaction

Areas for Improvement

1. Issue Triage: 216 unassigned issues (72%) need assignment to ensure accountability
2. Labeling: 59 unlabeled issues should be tagged for better categorization
3. User Experience Issues: Several copilot-cli issues ([tidy] Format JavaScript files with Prettier #1136, [WIP] Address feedback on "detection job" by removing dev.invalid.yml #1161, [WIP] Fix Codex tests for updated implementation #1218) report UX problems requiring quick resolution
4. Go Port Coordination: Multiple parallel PRs on Go port suggest need for coordination/merge strategy

Recommended Actions

1. Immediate: Assign owners to top 50 most commented unassigned issues
2. Short-term: Review and label all unlabeled issues within 2 weeks
3. Ongoing: Set up automated issue assignment based on labels/components
4. Strategic: Create a Go port tracking issue to coordinate Fix error pattern false positives in workflow validation #1501, Remove the Issue Summarizer workflow and update GenAI prompt generation #1502, Fix XML comment removal in imported workflows and add comprehensive test suite #1503 PRs

---

Full Data and Methodology

Data Collection

• Date Range: Issues and PRs updated between January 3, 2026 and February 2, 2026 (30 days)
• Repositories Analyzed: 200 public, non-archived repositories
• Issues Analyzed: 300 issues (sample from 1,448 total)
• PRs Analyzed: 300 pull requests (sample from 2,273 total)
• Data Source: GitHub API via GitHub MCP server

Methodology

Data Collection:

1. Discovered all public, non-archived repos using org:github archived:false query
2. Collected issues using org:github is:issue updated:>=2026-01-03 query
3. Collected PRs using org:github is:pr updated:>=2026-01-03 query
4. Added 3-5 second delays between API calls to respect rate limits

Analysis:

• Processed data using Python pandas for efficient DataFrame operations
• Activity scores calculated using weighted formula:
  • Repository score: issues × 2 + PRs × 3 + comments × 0.5
  • Author score: issues_opened × 2 + PRs_opened × 3
• Date comparisons done with timezone-aware timestamps (UTC)
• Stale items defined as: open for 30+ days with no updates in last 7 days
• Hot items defined as: created in last 30 days, sorted by comment count

Limitations:

• Metrics are based on a 300-item sample for issues and PRs (not full dataset)
• Only captures items updated in the last 30 days
• Activity scores favor repositories with both issues and PRs
• Bot activity included in contributor rankings

Tools Used

• GitHub MCP Server: GitHub API access via Model Context Protocol
• Python 3.13: Data processing and analysis
• Pandas 3.0.0: DataFrame operations and time-series analysis
• jq: JSON data transformation and aggregation

---

Generated: February 2, 2026 09:54 UTC
Workflow Run: §21585230911
Data Sample: 300 issues + 300 PRs from 1,448 issues + 2,273 PRs updated in last 30 days

AI generated by Organization Health Report

• expires on Feb 9, 2026, 9:59 AM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-02-09T09:59:06.687Z.

Closed by Workflow