How many stars does containers/initoverlayfs have?

GitHub currently reports 46 stars for containers/initoverlayfs, with about 3 of them added in the last 90 days.

How fast is initoverlayfs growing?

containers/initoverlayfs gained about 3 stars over the last 90 days of its history (about 3 in the last 30) — figures are approximate for older repos, whose star history is downsampled. That's in line with its lifetime average growth pace.

Is initoverlayfs still active?

containers/initoverlayfs is still attracting attention — about 3 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 initoverlayfs created?

containers/initoverlayfs was created on October 24, 2023 and earned its first GitHub star in Oct 2023.

containers/initoverlayfs

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

Open on GitHub

Stars: 46
History since: 2023
Latest star: Aug 2026

Star history

Last 30 days: +3
Last 90 days: +3
Stars / day: 0.0

Cumulative stars

FromTo

stars by date
Date	stars
October 24, 2023	1
October 25, 2023	3
October 27, 2023	5
October 30, 2023	6
November 3, 2023	8
November 6, 2023	9
November 9, 2023	10
November 23, 2023	11
November 29, 2023	12
December 2, 2023	13
December 4, 2023	14
December 7, 2023	18
December 12, 2023	21
December 13, 2023	24
December 25, 2023	25
December 26, 2023	26
January 20, 2024	27
January 24, 2024	28
February 5, 2024	29
February 7, 2024	30
March 8, 2024	31
May 10, 2024	32
May 13, 2024	33
May 31, 2024	34
August 17, 2024	35
September 23, 2024	36
October 8, 2024	37
November 18, 2024	38
April 3, 2025	39
June 10, 2025	40
August 26, 2025	41
September 23, 2025	42
October 9, 2025	43
August 27, 2026	45
August 28, 2026	46

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

The commit history reads containers/initoverlayfs 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 containers/initoverlayfs — Fix-labelled changes

File change frequency for containers/initoverlayfs — File change frequency

Bus factor for containers/initoverlayfs — Bus factor

Maintenance pulse for containers/initoverlayfs — Maintenance pulse

Contributors for containers/initoverlayfs — Contributors

Language activity for containers/initoverlayfs — Language activity

Commit activity for containers/initoverlayfs — Commit activity

Recent TODO/FIXME movement for containers/initoverlayfs — 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 containers/initoverlayfs.

Notes on containers/initoverlayfs

How many stars does containers/initoverlayfs have?: GitHub currently reports 46 stars for containers/initoverlayfs, with about 3 of them added in the last 90 days.
How fast is initoverlayfs growing?: containers/initoverlayfs gained about 3 stars over the last 90 days of its history (about 3 in the last 30) — figures are approximate for older repos, whose star history is downsampled. That's in line with its lifetime average growth pace.
Is initoverlayfs still active?: containers/initoverlayfs is still attracting attention — about 3 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 initoverlayfs created?: containers/initoverlayfs was created on October 24, 2023 and earned its first GitHub star in Oct 2023.

Read initoverlayfs 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 · containers/initoverlayfs star history

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