Analytics Report

tensorflow/tensorflow

Generated: Saturday, November 29, 2025 at 6:44:54 PM

Data Collection Summary

Collection Method: Full Repository Backup (Complete)

Analysis Period:

Start: Thu, Oct 30, 2025
End: Sat, Nov 29, 2025
Duration: 30 days

Data Types Analyzed:

Pull Requests: 986 items analyzed
Issues: ~84 items (estimated from ratio)
Releases: 0 items

Executive Summary

This analytics report provides data-driven insights into repository health, team dynamics, and development velocity.

Key Metrics Overview

Metric	Current Value	Interpretation
PR Merge Rate	45.4% (837/986 in period)	Needs Improvement
Review Coverage	0.0% (0/1845 total)	Needs Improvement
Active Contributors	36	Healthy
Bus Factor	2	High Risk
Deployment Frequency	0 releases	Low Activity

Critical Alerts

Critical Risk: Low bus factor indicates project vulnerability Quality Risk: More than half of PRs lack code review

Activity Analytics

Analysis Period: 10/30/2025 to 11/29/2025

Pull Request Metrics

Merge Rate: 45.4%
Merged PRs: 837
Closed (not merged): 149
Total PRs: 986

Issue Resolution

Average Resolution Time: 5.1 days (121 hours)
Median Resolution Time: 1.5 days (36 hours)

Activity Hotspots

Most Active Days:

#1 2025-11-29: 36 commits

👥 Contributor Analytics

Team Health

Bus Factor: 2 High Risk
- Indicates project risk if key contributors become unavailable
Active Contributors: 36 (last 90 days)
Contributor Mix: 30 new, 6 returning

Top Contributors

Contributor	PRs	Total Contributions
app/copybara-service	1789	1789
CodersAcademy006	8	8
ILCSFNO	4	4
Noam173	4	4
app/dependabot	3	3
Akarsh-28	3	3
AshiteshSingh	2	2
johnnynunez	2	2
newcomer119	2	2
ajayvnkt	2	2

Concentration of Contributions: The top contributor accounts for 97.0% of all contributions.

Label Analytics

Issue/PR Balance

Ratio: 1:0.09 (More PRs than issues)

Issue Lifecycle

Average Time Open: 5.1 days
Median Time Open: 1.5 days

Most Common Labels

type:bug
TF 2.19
comp:ops
ready to pull
TFLiteConverter

Label Distribution

Label	Count	Percentage
type:bug	92	18.5%
TF 2.19	50	10.0%
comp:ops	47	9.4%
ready to pull	40	8.0%
TFLiteConverter	39	7.8%
stat:awaiting response	26	5.2%
size:XS	22	4.4%
awaiting review	16	3.2%
comp:gpu	15	3.0%
2.17	15	3.0%

Code Health Metrics

Review Process

Review Coverage: 0.0% Needs Improvement
Reviewed PRs: 0 / 1845

Deployment Activity

Total Releases: 0 Low Activity

Trends (vs Previous Period)

Period-over-Period Comparison

Metric	Current	Previous	Δ	Trend
PR Merge Rate	45.4%	0.0%	+45.4%	Improving Improving
Active Contributors	36	0	+36	Improving Improving
Issue Resolution	5.1d	0.0d	+5.1d	Declining Declining

12-Week Velocity Trend

Velocity is increasing: 21900.0% change over 12 weeks (1 Stable 220 PRs/week)

🔮 Projections (Next 30 Days)

Based on current velocity and historical patterns:

Insufficient data for reliable projections.

Historical patterns are too limited to forecast accurately. Collect more data over time to enable predictive analysis.

Industry Benchmark Comparison

Compared against 50 similar-sized open source projects:

Metric	Your Repo	Median	Percentile	Interpretation
PR Merge Rate	45.4%	45.0%	⚪ 60th	Average (median)
Time to First Review	N/A	12.0h	95th	Excellent (top 10%)
Review Coverage	0.0%	72.0%	5th	Poor (bottom 25%)
Bus Factor	2	3	35th	Below average
Issue Resolution	5.1d	14.0d	80th	Good (top 25%)
Deployment Frequency	0.0/mo	2.0/mo	5th	Poor (bottom 25%)

Overall Score: 50/100

Your Position in the Industry

Analysis

Strengths (Above 75th percentile):

Issue Resolution Time (Days): 5.1d (🟡 good, 80th percentile)

Weaknesses (Below 50th percentile):

Review Coverage: 0.0% (🔴 poor, 5th percentile)
Bus Factor: 2 (🟠 below_average, 35th percentile)
Deployment Frequency: 0.0/month (🔴 poor, 5th percentile)

Recommendations (Priority Order):

Increase review coverage by 85% to reach 75th percentile (85%)
CRITICAL: Bus factor is 2 (risky). Aim for at least 3-5 core contributors
app/copybara-service contributes 97% of work
Increase deployment frequency to at least 2.0/month
Consider automated releases for merged PRs or weekly release cadence

📖 Executive Narrative

The Story This Data Tells

Executive Summary: tensorflow

tensorflow demonstrates healthy development practices with 0% review coverage and 45% PR merge rate.

Key Observations

📈 Velocity improving: 2 out of 4 key metrics show positive trends
🔴 2 metrics below industry standards (require immediate attention)
⚠️ Single contributor dominance: app/copybara-service accounts for 97% of contributions

Root Cause Analysis

Low deployment frequency despite active development

Hypothesis: Manual release process or CI/CD pipeline may be bottleneck preventing frequent deployments

Supporting Evidence:

0 releases in analysis period
837 PRs merged but not released
Potential 837 PRs per release

Recommended Actions (Priority Order)

🥇 Critical

Audit and resolve 10 stalled PRs

Rationale: PRs waiting >3 days represent blocked work and frustrated contributors. Quick wins available by clearing backlog.
Expected Impact: Improve merge rate by ~1%
Timeframe: This week

🥉 Enhance

Increase deployment cadence

Rationale: Current: 0.0/month, Industry median: 2.0/month
Expected Impact: Faster feedback loops, improved velocity
Timeframe: 1-2 months

Projected Outcome

If no action is taken:

Contributor frustration will increase, potentially leading to abandonment

If priority actions are taken:

Improve merge rate by ~1%
Faster feedback loops, improved velocity

Risk Assessment

Risk Level: 🟠 High

🟠 High dependency risk: Bus factor is only 2

Items Requiring Attention

PRs Aging Out (>7 days without merge)

#	Title	Author	Created	Waiting	Status
#103319	[PoC] Test trilom/file-changes-action CVE-2025-30066 via malicious filename	@QxCV2	29d ago	[CRITICAL] 29.9d	No reviewers
#103320	[xla:pjrt] Remove PjRtFuture type alias	@app/copybara-service	29d ago	[CRITICAL] 29.9d	No reviewers
#103321	Remove all usages of arguments_are_tupled since the default is false and it is	@app/copybara-service	29d ago	[CRITICAL] 29.9d	No reviewers
#103322	Map CudaGraph Node in traceviewer could show per-node framework namescope by rewrite their annotation to the value during its corresponing creation.	@app/copybara-service	29d ago	[CRITICAL] 29.9d	No reviewers
#103323	Use ABSL_LOG instead of LOG to avoid name collisions with other projects.	@app/copybara-service	29d ago	[CRITICAL] 29.9d	No reviewers
#103324	Fix: near-singular matrix check for GPU	@Navya1707	29d ago	[CRITICAL] 29.9d	No reviewers
#103325	[ReplicaGroupV3][Validation] Add validation for `Mesh` and `AxisRef` constructors.	@app/copybara-service	29d ago	[CRITICAL] 29.9d	No reviewers
#103326	[xla:ffi] Add iterator to traverse Dictionary	@app/copybara-service	29d ago	[CRITICAL] 29.8d	No reviewers
#103327	Automated Code Change	@app/copybara-service	29d ago	[CRITICAL] 29.8d	No reviewers
#103328	Unify topology in PjRtTopologyDescription	@app/copybara-service	29d ago	[CRITICAL] 29.7d	No reviewers

Legend: "Created" = Days since PR was created | "Waiting" = Days without merge progress

Value at risk: 10 stalled PRs (~580 hours of work, created avg 29d ago)

Business Impact: Delayed features, frustrated contributors, potential technical debt

Actions:

Review PR status and unblock bottlenecks (priority: PRs >14 days old)
Request author updates if waiting on changes
Auto-merge approved PRs with passing CI

Insights & Recommendations

1. Moderate PR Merge Rate (45.4%)

Note: Some high-quality projects maintain merge rates in 25-40% range by design
If above benchmark: maintain current standards
If trending down: investigate recent process changes
Consider benchmark data: industry median is 45.0%

2. Review Coverage Needs Improvement (0.0%)

Action: 1845 PRs were merged without review
Next Steps:
- Enable "Require approvals" in branch protection
- Set up CODEOWNERS file for automatic review assignment
- Schedule code review training session

3. Critical: Low Bus Factor (2)

Risk: app/copybara-service accounts for 97.0% of contributions
Immediate Actions:
- Document critical systems and processes
- Implement pair programming sessions
- Create onboarding documentation for new contributors
- Schedule knowledge transfer sessions

4. High Contribution Concentration (97.0%)

Top contributor dominates contributions
Risk of knowledge silos
Encourage broader participation

5. Fast Issue Resolution (5.1 days avg)

Excellent responsiveness
Maintain current triage process

Report Metadata

Report Generated: 11/29/2025, 6:44:54 PM

Data Collection Mode: Full Repository Backup (Complete)

Period Analyzed:

From: October 30, 2025
To: November 29, 2025

Analysis Duration:

Activity: 1.73s
Contributors: 1.07s
Labels: 1.60s
Health: 1.15s

Generated by: GitHub Extractor CLI (ghextractor) Version: n/a