How many stars does jgthms/euro-2016-calendar have?

GitHub currently reports 6 stars for jgthms/euro-2016-calendar. 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 euro-2016-calendar?

gitdebt observed about 1 public star actions for jgthms/euro-2016-calendar 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 faster than its lifetime average activity pace.

Is euro-2016-calendar still active?

Public archive data shows about 1 star actions for jgthms/euro-2016-calendar in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.

When was euro-2016-calendar created?

jgthms/euro-2016-calendar was created on June 11, 2016. The first public star activity observed for jgthms/euro-2016-calendar is from Jun 2016.

jgthms/euro-2016-calendar

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

Open on GitHub

Current stars: 6
Activity since: 2016
Latest activity: Apr 2019

Public star activity

Last 30 days: +1
Last 90 days: +1
Actions / day: 0.0

Public star actions

FromTo

stars by date
Date	stars
June 12, 2016	1
June 13, 2016	2
July 5, 2016	3
July 27, 2016	4
July 28, 2016	5
July 30, 2016	6
December 22, 2016	7
April 26, 2019	8

The last 90 days run ahead of this repository's lifetime average.

The commit history reads jgthms/euro-2016-calendar 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 for jgthms/euro-2016-calendar — Fix-labelled changes

File change frequency for jgthms/euro-2016-calendar — File change frequency

Bus factor for jgthms/euro-2016-calendar — Bus factor

Maintenance pulse for jgthms/euro-2016-calendar — Maintenance pulse

Contributors for jgthms/euro-2016-calendar — Contributors

Language activity for jgthms/euro-2016-calendar — Language activity

Commit activity for jgthms/euro-2016-calendar — Commit activity

Recent TODO/FIXME movement for jgthms/euro-2016-calendar — Recent TODO/FIXME movement

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 jgthms/euro-2016-calendar.

Notes on jgthms/euro-2016-calendar

How many stars does jgthms/euro-2016-calendar have?: GitHub currently reports 6 stars for jgthms/euro-2016-calendar. 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 euro-2016-calendar?: gitdebt observed about 1 public star actions for jgthms/euro-2016-calendar 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 faster than its lifetime average activity pace.
Is euro-2016-calendar still active?: Public archive data shows about 1 star actions for jgthms/euro-2016-calendar in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was euro-2016-calendar created?: jgthms/euro-2016-calendar was created on June 11, 2016. The first public star activity observed for jgthms/euro-2016-calendar is from Jun 2016.

Read euro-2016-calendar against a neighbour

comparison builder

Compare with any repository

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 · jgthms/euro-2016-calendar star history

<a href="https://gitdebt.com/jgthms/euro-2016-calendar?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/jgthms/euro-2016-calendar/chart.svg?theme=dark" />
    <img alt="jgthms/euro-2016-calendar star history" src="https://api.gitdebt.com/api/repos/jgthms/euro-2016-calendar/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through April 26, 2019 · Still updating — <a href="https://gitdebt.com/jgthms/euro-2016-calendar?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.