Skip to content

nousresearch/storywriter

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

Open on GitHub
Stars
12
History since
2025
Latest star
Nov 2026

Star history

Last 30 days
+2
Last 90 days
+3
Stars / day
0.0
Cumulative stars

stars from November 19, 2025 to November 9, 2026, peaking at 12.12 STARS1 YR12NOV 2026NOV 2025

12 stars on November 9, 2026.

stars by date
Datestars
November 19, 20251
March 8, 20262
April 3, 20263
May 2, 20264
May 27, 20265
June 5, 20266
July 7, 20267
July 10, 20268
July 30, 20269
September 10, 202610
November 2, 202611
November 9, 202612

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

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

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 nousresearch/storywriter.

Notes on nousresearch/storywriter

How many stars does nousresearch/storywriter have?
GitHub currently reports 12 stars for nousresearch/storywriter, with about 3 of them added in the last 90 days.
How fast is storywriter growing?
nousresearch/storywriter gained about 3 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. That's in line with its lifetime average growth pace.
Is storywriter still active?
nousresearch/storywriter 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 storywriter created?
nousresearch/storywriter was created on March 19, 2025 and earned its first GitHub star in Nov 2025.

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