Engagement patterns
Start with stars, forks, and concentration metrics to see whether attention is broadly distributed or captured by a small elite of repositories.
Analysis
This page brings together the project's analytical layer: engagement, activity, quality, and concentration. The goal is not just to describe repositories, but to explain which signals are most closely associated with visibility and sustained adoption.
Interactive Analysis
Impact levels follow the SQL view logic from the project: High Impact is at least 10 stars, Medium Impact is 3 to 9 stars, Low Impact is 1 to 2 stars, and Early Stage is 0 stars.
Start with stars, forks, and concentration metrics to see whether attention is broadly distributed or captured by a small elite of repositories.
Use commits, active-days measures, and the lifecycle curve to distinguish short-lived repositories from sustained, higher-maturity projects.
Compare README coverage and community-health signals to evaluate whether project packaging and maintainability align with visibility.
The KPI row emphasizes normalized quality and engagement metrics such as average stars per repository, README adoption, impact-tier share, and concentration rather than simple totals.
Use filters to compare whether high-impact subsets also show stronger documentation, longer active lifespan, and better reuse signals through forks.
Move from KPIs to distributions, then to scatter and lifecycle views, and finish with the repository spotlight to inspect the projects driving the aggregate patterns.
Impact tiers are computed with the same SQL view logic used in the project write-up. This plot shows how the current filtered subset is distributed across those four visibility bands.
Each point represents one repository in the filtered view. The x-axis uses log-scaled forks, the y-axis uses log-scaled stars, point size reflects commit volume, and point color follows the impact-level classification.
This curve shows the cumulative share of repositories that reach each active-days band, from 0 to 30 days through 3 or more years. It summarizes how quickly repository activity falls off over time.
Each tile stands for one repository, up to 120 repositories in the current filtered view. Darker tiles indicate higher community-health scores, while lighter tiles indicate missing or weak health signals.
| Repository | Owner | Language | Impact | Stars | Forks | Commits | Active Days |
|---|