Skip to content

electerious/fsify

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

Open on GitHub
Current stars
28
Activity since
2017
Latest activity
Oct 2025

Public star activity

Last 30 days
+1
Last 90 days
+1
Actions / day
0.0
Public star actions

stars from February 18, 2017 to October 3, 2025, peaking at 30.30 STARS8 YR 7 MO30OCT 2025FEB 2017

30 stars on October 3, 2025.

stars by date
Datestars
February 18, 20171
June 12, 20172
June 29, 20173
February 20, 20185
March 11, 20186
September 11, 20187
September 12, 20188
October 26, 20189
October 29, 201810
October 31, 201811
January 6, 201912
October 15, 201913
March 5, 202014
March 22, 202015
April 28, 202016
January 25, 202117
April 13, 202118
April 29, 202119
June 24, 202120
June 27, 202121
June 29, 202124
July 7, 202225
August 2, 202226
February 22, 202327
October 20, 202328
April 7, 202529
October 3, 202530

The last 90 days run in line with its lifetime average.

The commit history reads electerious/fsify 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 electerious/fsify
File change frequency
File change frequency for electerious/fsify
Bus factor
Bus factor for electerious/fsify
Maintenance pulse
Maintenance pulse for electerious/fsify
Contributors
Contributors for electerious/fsify
Language activity
Language activity for electerious/fsify
Commit activity
Commit activity for electerious/fsify
Recent TODO/FIXME movement
Recent TODO/FIXME movement for electerious/fsify

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 electerious/fsify.

Notes on electerious/fsify

How many stars does electerious/fsify have?
GitHub currently reports 28 stars for electerious/fsify. 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 fsify?
gitdebt observed about 1 public star actions for electerious/fsify over the latest 90 days of archive coverage (about 1 in the latest 30). This is an approximate attention signal, not a net-star count, because unstars are not present. That's in line with its lifetime average activity pace.
Is fsify still active?
Public archive data shows about 1 star actions for electerious/fsify in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was fsify created?
electerious/fsify was created on February 13, 2017. The first public star activity observed for electerious/fsify is from Feb 2017.

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

<sub>Star history source: Historical star data · Covers through October 3, 2025 · Still updating — <a href="https://gitdebt.com/electerious/fsify?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.