Skip to content

getify/elasi

Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.

Open on GitHub
Stars
63
History since
2022
Latest star
Jun 2026

Star history

Last 30 days
+1
Last 90 days
+1
Stars / day
0.0
Cumulative stars

stars from October 13, 2022 to June 3, 2026, peaking at 63.63 STARS3 YR 8 MO63JUN 2026OCT 2022

63 stars on June 3, 2026.

stars by date
Datestars
October 13, 20224
October 14, 20225
October 15, 20226
October 17, 20228
October 19, 20229
December 15, 202227
December 16, 202245
December 17, 202248
December 18, 202249
December 21, 202250
December 22, 202251
December 23, 202252
December 24, 202253
December 26, 202254
December 27, 202255
December 28, 202257
January 27, 202358
July 8, 202459
July 30, 202460
October 26, 202461
August 30, 202562
June 3, 202663

The last 90 days run behind its lifetime average, which is ordinary for a mature project.

The commit history reads getify/elasi a second time

methodology

Fix-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.

Fix-labelled changes
Fix-labelled changes for getify/elasi
File change frequency
File change frequency for getify/elasi
Bus factor
Bus factor for getify/elasi
Maintenance pulse
Maintenance pulse for getify/elasi
Contributors
Contributors for getify/elasi
Language activity
Language activity for getify/elasi
Commit activity
Commit activity for getify/elasi
Recent TODO/FIXME movement
Recent TODO/FIXME movement for getify/elasi

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 studio

Maintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.

Reading badge evidence for getify/elasi.

Notes on getify/elasi

How many stars does getify/elasi have?
GitHub currently reports 63 stars for getify/elasi, with about 1 of them added in the last 90 days.
How fast is elasi growing?
getify/elasi 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 below its lifetime average growth pace, which is common for mature projects.
Is elasi still active?
getify/elasi 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 elasi created?
getify/elasi was created on October 13, 2022 and earned its first GitHub star in Oct 2022.

Put this drawing in your README

markdown for agents

The 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.

README.md · getify/elasi star history
<a href="https://gitdebt.com/getify/elasi?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/getify/elasi/chart.svg?theme=dark" />
    <img alt="getify/elasi star history" src="https://api.gitdebt.com/api/repos/getify/elasi/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/getify/elasi?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.