Devthropology: Analyzing GitHub Repository Health and Contributor Dynamics

Devthropology is a technical analysis platform designed to extract deeper insights from GitHub repositories than standard git statistics provide. By focusing on contributor dynamics, filesystem relationships, and merge velocity, it allows maintainers and stakeholders to evaluate the long-term health and sustainability of a codebase.

Repository Health and Scale Metrics

Devthropology provides a high-level overview of a repository's scale and activity levels to establish a baseline for project health. Using the getsentry/sentry repository as a benchmark, the tool tracks several key scale indicators:

• Contributor Volume: Total contributors versus active contributors over a three-month window (e.g., 1,222 total vs. 211 active).
• Codebase Scale: Estimated lines of code (LOC) and total file counts (e.g., 5.18 million LOC across 18,960 files).
• Language Distribution: A breakdown of the codebase by language percentage and size, identifying the primary drivers of the project's technical stack (e.g., Python and TypeScript/TSX).
• Activity Lifespan: Tracking the time elapsed since the first and last recorded activity to determine project longevity.

Contributor Dynamics and Churn Tracking

A core feature of Devthropology is its ability to monitor the flow of human capital within a project. This allows teams to identify whether a project is growing its contributor base or suffering from attrition.

New Contributor Onboarding

The tool tracks new contributors added within the last 30 days, providing a list of individuals and bots that have recently begun contributing to the project.

Contributor Churn

Devthropology identifies "churned" contributors—those who were active but have remained inactive for 30 to 60 days. Tracking churn is critical for identifying potential knowledge loss or bottlenecks in the contributor pipeline.

Author Tenure

The platform calculates the median author age (tenure) for contributors active in the last three months. This metric helps distinguish between projects driven by a small group of long-term veterans and those with a high turnover of short-term contributors.

Engineering Velocity and Throughput

Devthropology measures the efficiency of the development pipeline by tracking how code moves from proposal to merge.

Time to Merge

The tool monitors the average time it takes for a Pull Request (PR) to be merged, providing comparisons between the last 7 days and the last 30 days to identify trends in review speed.

PR and Line Throughput

Velocity is further quantified through:

• Merged PR Volume: The total number of PRs merged within specific timeframes.
• Lines Changed: A detailed count of additions and deletions, showing the net growth or shrinkage of the codebase.
• Files Changed: The total number of unique files modified, which indicates the breadth of changes across the system.

Exploration and Reporting Tools

Beyond high-level metrics, Devthropology offers specific modules for deeper exploration:

• Filesystem Exploration: Analysis of how the codebase is structured.
• Relationship Mapping: Visualizing how different parts of the project or different contributors interact.
• Trends Analysis: Tracking the trajectory of the aforementioned metrics over time.
• Role-Based Reports: Dedicated reports for "Authors" and "Reviewers" to analyze the balance of work between those writing code and those auditing it.