continuedev/continue-fork
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Stars
- 8
- History since
- 2026
- Latest star
- Sep 2026
Star history
- Last 30 days
- +2
- Last 90 days
- +8
- Stars / day
- 0.1
8 stars on September 8, 2026.
| Date | stars |
|---|---|
| June 12, 2026 | 1 |
| June 18, 2026 | 2 |
| June 22, 2026 | 3 |
| June 26, 2026 | 4 |
| July 4, 2026 | 5 |
| July 12, 2026 | 6 |
| August 22, 2026 | 7 |
| September 8, 2026 | 8 |
The commit history reads continuedev/continue-fork 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 continuedev/continue-fork.
Notes on continuedev/continue-fork
- How many stars does continuedev/continue-fork have?
- GitHub currently reports 8 stars for continuedev/continue-fork, with about 8 of them added in the last 90 days.
- How fast is continue-fork growing?
- continuedev/continue-fork gained about 8 stars over the last 90 days of its history (about 2 in the last 30) — figures are approximate for older repos, whose star history is downsampled.
- Is continue-fork still active?
- continuedev/continue-fork is still attracting attention — about 2 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 continue-fork created?
- continuedev/continue-fork was created on March 11, 2026 and earned its first GitHub star in Jun 2026.
Read continue-fork 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/continuedev/continue-fork?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/continuedev/continue-fork/chart.svg?theme=dark" />
<img alt="continuedev/continue-fork star history" src="https://api.gitdebt.com/api/repos/continuedev/continue-fork/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/continuedev/continue-fork?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.