preactjs/benchmarks
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Stars
- 3
- History since
- 2025
- Latest star
- Jul 2026
Star history
- Last 30 days
- +1
- Last 90 days
- +1
- Stars / day
- 0.0
3 stars on July 1, 2026.
| Date | stars |
|---|---|
| April 9, 2025 | 1 |
| January 19, 2026 | 2 |
| July 1, 2026 | 3 |
The last 90 days run ahead of this repository's lifetime average.
The commit history reads preactjs/benchmarks 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 preactjs/benchmarks.
Notes on preactjs/benchmarks
- How many stars does preactjs/benchmarks have?
- GitHub currently reports 3 stars for preactjs/benchmarks, with about 1 of them added in the last 90 days.
- How fast is benchmarks growing?
- preactjs/benchmarks gained about 1 stars over the last 90 days of its history (about 1 in the last 30) — figures are approximate for older repos, whose star history is downsampled. That's faster than its lifetime average growth pace.
- Is benchmarks still active?
- preactjs/benchmarks is still attracting attention — about 1 new GitHub stars in the most recent 30 days of its history. For commit-level signals, see the commit activity heatmap, commit trend, and contributors charts on this page.
- When was benchmarks created?
- preactjs/benchmarks was created on December 17, 2022 and earned its first GitHub star in Apr 2025.
Read benchmarks 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/preactjs/benchmarks?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/preactjs/benchmarks/chart.svg?theme=dark" />
<img alt="preactjs/benchmarks star history" src="https://api.gitdebt.com/api/repos/preactjs/benchmarks/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: GitHub star history · Covers through November 14, 2026 · Still updating — <a href="https://gitdebt.com/preactjs/benchmarks?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.