denoland/benchmark_data
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 21
- Activity since
- 2020
- Latest activity
- Aug 2025
Public star activity
- Last 30 days
- +2
- Last 90 days
- +2
- Actions / day
- 0.0
22 stars on August 30, 2025.
| Date | stars |
|---|---|
| March 6, 2020 | 1 |
| April 22, 2020 | 2 |
| May 16, 2020 | 3 |
| May 20, 2020 | 5 |
| May 21, 2020 | 6 |
| May 27, 2020 | 7 |
| June 18, 2020 | 8 |
| November 10, 2020 | 9 |
| March 15, 2021 | 10 |
| May 6, 2021 | 11 |
| July 4, 2021 | 12 |
| October 6, 2022 | 13 |
| October 21, 2022 | 14 |
| October 31, 2022 | 15 |
| June 6, 2023 | 16 |
| October 10, 2023 | 17 |
| November 2, 2023 | 18 |
| November 22, 2024 | 19 |
| March 29, 2025 | 20 |
| August 24, 2025 | 21 |
| August 30, 2025 | 22 |
The last 90 days run ahead of this repository's lifetime average.
The commit history reads denoland/benchmark_data a second time
methodologyFix-labelled changes, file change frequency, ownership concentration and maintenance cadence, each computed from this repository's analyzed commit window. None of them is derived from stars, which is why they are allowed to disagree with the curve above.
Attention is not adoption.
Stars against usage
No published package was detected for this repository, so there is nothing to lay over star growth.
Earned badges
badge studioMaintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.
Reading badge evidence for denoland/benchmark_data.
Notes on denoland/benchmark_data
- How many stars does denoland/benchmark_data have?
- GitHub currently reports 21 stars for denoland/benchmark_data. The chart itself is rebuilt from historical star data, which records star actions and not unstars, so it reads as an attention signal rather than a net star count.
- What does recent star activity look like for benchmark_data?
- gitdebt observed about 2 public star actions for denoland/benchmark_data over the latest 90 days of archive coverage (about 2 in the latest 30). This is an approximate attention signal, not a net-star count, because unstars are not present. That's faster than its lifetime average activity pace.
- Is benchmark_data still active?
- Public archive data shows about 2 star actions for denoland/benchmark_data in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
- When was benchmark_data created?
- denoland/benchmark_data was created on March 6, 2020. The first public star activity observed for denoland/benchmark_data is from Mar 2020.
Read benchmark_data against a neighbour
comparison builderPut this drawing in your README
markdown for agentsThe block below publishes the chart with its source and coverage date stated beside it — the same three facts the title block above shows, as text a reader can check. The prompt underneath hands a coding agent the badges and repo-health charts as well.
<a href="https://gitdebt.com/denoland/benchmark_data?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/denoland/benchmark_data/chart.svg?theme=dark" />
<img alt="denoland/benchmark_data star history" src="https://api.gitdebt.com/api/repos/denoland/benchmark_data/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through August 30, 2025 · Still updating — <a href="https://gitdebt.com/denoland/benchmark_data?ref=readme">gitdebt</a></sub>Light and dark variants, alt text, and one provenance line. Provenance is text in your README, never baked into the image URL, so the chart stays cacheable.
Paste it into Claude Code, Cursor, Codex, or any coding agent with your checkout open. It carries the measured numbers, the exact snippets, and the rules — including replacing an existing star-history widget in place rather than stacking a second chart under it.