# 618 stars, 39 downloads: a Russian-language Windows log viewer, the stars are bought · GitHub open-source project

> Source: https://stringers.io/en/github/gh_Illson__RustText.html (Stringers / 什么值得做, generated 2026-11-20)
> Stringers tracks which small products suddenly took off each day, investigates why one by one, and distils playbooks from them. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these investigations and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools feed (daily breakouts) / plays (playbooks) / hot / products / data. Setup: https://github.com/komako-workshop/stringers (the user signs in with Google at stringers.io/en/start.html to get a personal URL). Site index: https://stringers.io/llms.txt

> It never really took off: nearly all the stars came from farm accounts, registered less than six months ago, with 0 followers, and on the same days they were also starring a batch of other repos like SoduWork and Antigravity. Downloads total only 39, with 2 forks, and nobody talks about it off-GitHub.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-18

Illson/RustText · Illson

# 618 stars, 39 downloads: a Russian-language Windows log viewer, the stars are bought

**What it is** A Russian-language replacement for Windows Notepad, written in Rust. It recovers closed tabs, keeps unsaved drafts, and opens large logs page by page. One developer used an AI agent to write the code.

**Why it went viral** It didn't really: almost all the stars came from farm accounts, which were registered less than half a year ago, have 0 followers, and starred a batch of other repos like SoduWork and Antigravity the same day. Downloads are only 39, forks 2, and nobody discusses it outside the repo.

**D** **How you could follow it** Don't. Whether you copy it as an editor or buy stars like it, neither works. What's worth taking is how to spot star farming (forks are 1% of stars, downloads far below stars, starrers are new accounts), along with its workflow of one person plus an AI agent working from issues and merging after CI passes. If you really want to build a log tool, start from specific pain points klogg and lnav haven't solved.

Grade D: the growth was manufactured, and there is no real demand signal to follow. The product is a notepad, a category Notepad++, klogg and Zed already cover, with no new angle. Only worth understanding as an example of how to recognize this kind of curve. Few people know about it yet

Data (updated daily) · repo created 2026-11-16 · 402 stars

GitHub · stars

Data 2026-11-18 → 2026-11-20 (3 days, 3 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

RustText is a text editor and large-log viewer a Russian developer built for himself on Windows, written in Rust, with a README entirely in Russian. On the third day after creation it reached 618 stars, gaining 520 in a single day, and even appeared on a Chinese "new repo star gainers" chart. But the installers across its 8 releases have only been downloaded 39 times. Spot-checking the accounts that starred it, most were registered a few months earlier, have 0 followers and 0 repos, and were starring another batch of repos the same day. Below: how these stars were produced, how to spot it at a glance, and what someone trying to get real stars for a similar project can learn from it.

### On the day it was created, one person published five releases.

Nov 2026 16 17:32 (UTC), GitHub user Illson pushed the first three commits of RustText in one sitting, 17:46 setting up the repo. 19:12 Shipped v0.1.0, then before midnight pushed v0.1.1 through v0.1.4, five releases in one night. 23:57 He opened an issue titled with a single word, 「адд」 ("add", a casual Russian spelling), and under it 13 jotted ideas: 「wide scrollbar with a minimap」「content scrolls along when dragging the big-log slider」「right-click menu, open txt, json, xml, log by default」「remove the 8 MiB limit and the 1-million-line cap on line generation」.

That's the project's shape: the author writes the requirements, and an AI coding agent writes the code. The repo's AGENTS.md says each task gets its own work branch named `codex/<task>`, PRs follow a template of 「goal / linked issue / changes」, and nothing merges until CI passes. In three days it had 41 commits and 8 releases, with issue and PR numbers reaching #55. The two most recent threads are already discussing a rewrite of the whole project as a single .NET + Avalonia exe.

It's been diligent, but it's a one-person tool for personal use. Nov 17 evening, the first 「users」 showed up.

### What it is

A Windows x64 Notepad replacement, written in Rust with GPUI Kit (the community build of the UI framework behind the Zed editor). Features: multiple tabs, the last 100 closed tabs can be restored, unsaved drafts survive a restart; files over 8 MiB or 50k lines automatically switch to paged viewing; shows encoding and line endings, can validate JSON; double-clicking a file hands it to an already-open window. The README runs about 24 KB, documenting every shortcut and every limit in detail (GitHub README, 11-19).

Author Illson's account was registered in 2019, has 0 followers, and of 8 public repos, 7 are forks of scraper and automation libraries. The only original work is RDPForm with 0 stars and this RustText. The other two people who opened PRs and forked the repo are Russian accounts registered in 2022 that look like a real person's, probably a colleague or friend of the author.

### 618 stars, 39 downloads

| Timeline | star | fork | Notes |
|---|---|---|---|
| 11-16 17:46 | 0 | 0 | Repo created |
| 11-18 | 88 | 2 | GitHub daily snapshot |
| 11-19 | 608 | 2 | Single day +520 |
| 11-19 daytime | 618 | 2 | GitHub API; 1 watcher, the author himself |

Download counts for RustText.zip across the 8 releases are 5, 4, 4, 4, 8, 4, 4, 6, totaling 39 (GitHub Releases, 11-19). The number of people who starred it is 16 times the number who downloaded it.

Compare forks too. Among repos created in under 10 days that gained over 300 stars in a single day in the same period, fork-to-star ratios ran between 7% and 24%. RustText is 2 to 618,0.3%, an order of magnitude lower, and both of its forks come from people the author knows.

It can't be found off-platform either. Hacker News, Reddit, X, and the Russian tech community Habr turn up not a single discussion. The only places listing it are a few Chinese GitHub star-trend aggregators, one of which ranks it #32 on its 「new repos this week by stars」 board. Those sites pick up repos automatically from star counts, so they reflect the stars, not the cause.

### Who gave these stars

I couldn't get the full list of stargazers, so I used GH Archive, a public event archive that records part of GitHub's star events hourly. Between Nov 16 and 19, it sampled 7 accounts that starred RustText:

| Time (UTC) | Account | Registration date | Followers / repos |
|---|---|---|---|
| 11-17 19:39 | Dobroezzhev1981 | 2026-08-16 | 0 / 0 |
| 11-18 00:09 | brilliantnamira-lang | — | Deleted by GitHub |
| 11-18 03:21 | chaesacorporate-beep | 2026-06-30 | 0 / 13 |
| 11-18 05:23 | mahfuz6701 | 2026-06-17 | 1 / 0 |
| 11-18 05:58 | pjhulki60-code | 2026-10-06 | 0 / 13 |
| 11-18 06:19 | ronu80691-stack | 2026-10-24 | 0 / 0 |
| 11-18 18:15 | nzaleta | 2026-11-02 | 0 / 0 |

Of the 7, 6 are obviously off: accounts under six months old, no followers, no original code; several have the auto-generated names GitHub suggests at signup, ending in `-lang`, `-beep`, `-code`, `-stack`; and one has already been banned by GitHub. Only mahfuz6701 is unclear.

Listing the repos these accounts starred shows heavy overlap. Nearly every account starred the same few: mdiri-ai/SoduWork, loysger/Antigravity, Check-Risk-WAF, beenuar/AiSOC, NPMscan/npmscan-action, tetiva-app/client; plus a whole cluster of "something-osint-something" repos using one naming template (legwork-osint-ai-investigator, gazette-osint-company-registries, amber-osint-web-archive…), whose author names are random nouns stuck together. These repos also have unusually few forks: Check-Risk-WAF 2,278 stars / 10 forks, Antigravity 1,247 / 4, npmscan-action 510 / 1.

The timing matches too. On Nov 19, SoduWork gained 1,135, Antigravity gained 200, Check-Risk-WAF gained 129, and RustText gained 520, all on the same day (GitHub daily snapshots). Looking further back, stars started arriving the day after the repo was created, slowly accumulating to 88, then a single batch of over 500 more. That looks like a star-farming package delivered in installments to appear natural (inference). Many of these 「customers」 are Russian-speaking projects (1C plugins, a VPN client, an MTProto library), which fits RustText's origins, so this may be a star-buying service with a Russian-speaking client base (inference, unverified).

What we can confirm: of these 618 stars, only a single digit to a dozen or so were likely given by real people. The sample covered only 7 accounts, so the exact proportion can't be calculated. Who paid, where they bought it, and how much, none of that is visible. The author has no website, no paid offering, and no résumé or hiring link in the README, so what this star inflation is for isn't visible from outside.

### How many like it

Even if the stars were genuine, this product would struggle to win stars from strangers, because what it does has been done well by others:

| Product | Scale | Compared with RustText |
|---|---|---|
| Windows built-in Notepad | Built into the system | Has had tabs and auto-save since 2023; it already has RustText's 「draft survives restart」 |
| Notepad++ | 29.9k stars, the de facto standard on Windows | Far more features and plugins |
| Notepad4 | 5.1k star | Lightweight Windows Notepad alternatives |
| EmEditor, Sublime Text | Commercial software | Opening multi-GB files and split views, which RustText still has queued in its issues |
| klogg | 3.6k star | Dedicated cross-platform large-log viewers with filtering and highlighting |
| lnav | 10.8k star | Viewing logs in a terminal with structured parsing |
| Zed | 95k star | A full editor on the same GPUI stack, already supporting Windows |

Data from GitHub, 11-19.

What RustText has beyond that is a Russian-language UI, and one person plus AI shipping several releases a day. The first narrows its audience to Russian speakers; the second is a development method, not a feature users care about.

### If it were you

**Verdict:** Don't follow it. RustText didn't break out; its stars were bought, and the product has nothing nobody else has built. What's useful to you is two things: how to spot a starred-up repo at a glance, and its 「one person + AI agent」 open-source workflow.

**Who it's for:** developers thinking about open-source projects who are anxious about every new repo gaining hundreds of stars in three days. After reading this you can relax: many of those curves are fake. Anyone who wants to run an open-source project solo with agents like Codex or Claude Code can read its AGENTS.md and PR template.

**Who it's not for:** anyone who wants to copy it as a Windows editor or log viewer to collect stars. That path already has the built-in Notepad, Notepad++, klogg, and Zed, and without a fresh angle it's hard to stand out. Anyone thinking of buying stars the same way should not: GitHub bans farmed accounts, and one in the sample has already been deleted. Star-trend sites will list you for a few days, but download and fork counts give the game away, and anyone who knows the space will see through it.

**How to spot star farming:** check three numbers first. Forks are under 1% of stars; release downloads are far below stars; the only watcher is the author. Then open a few of the accounts that starred it and see whether they registered this year, have 0 followers and 0 repos, and whether the repos they starred are the same batch. If the three numbers are off and the accounts match, it's almost certainly farmed.

**How to do it (if you want a real competitor that earns stars):** don't start with "yet another Notepad." Start with a specific pain point, something klogg and lnav haven't solved: put AI into log viewing, so you can select an error and ask "what's wrong here" directly; or build a viewer for one kind of log (Kubernetes, game servers, Android logcat). Write the README in English and lead with an animated GIF so people understand it in ten seconds. You can borrow RustText's workflow: have an agent work through issues one by one, run every change through CI, and release often.

**How to get users:** real stars come from real people seeing the project: post a Show HN, r/rust or the relevant ecosystem subreddit, and share a screen recording on X of "opening a 5 GB log in 1 seconds." A post that explains clearly "why I built yet another log viewer and how it beats klogg" will do more than any trending list.

**When to move:** there's no rush. This isn't a window-of-opportunity play, and RustText itself won't take anyone's spot.

**What would show this read was wrong:** if RustText's release downloads climb to hundreds or thousands over the next few weeks, and forks and issues show unfamiliar real users, or someone recommends it unprompted on Habr or r/rust, then it has real users and I misjudged a niche good tool as a star-farm. Conversely, if its stars suddenly drop sharply, that means GitHub cleaned up the farmed accounts.

[GitHub repo ↗](https://github.com/Illson/RustText)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| Notepad++ | Open source | 2003(GitHub 2015) | 29.9k stars, the Windows standard | Far more features and plugins; RustText only adds paged large files and draft recovery |
| Windows Notepad (tabs / session restore) | Big-company features | 2023 | Built into the system | Already has tabs and an auto-saving draft notepad |
| EmEditor / Sublime Text | Other | 1997 / 2008 | Commercial large-file editor | Huge files and split views, which RustText still lists as TODO in its issues |
| klogg | Open source | 2016 | 3.6k star | Professional cross-platform large-log viewer with filtering and highlighting |
| LogExpert | Open source | 2017 | 1.2k star | tail and log analysis tools for Windows |
| lnav | Open source | 2009 | 10.8k star | Viewing logs in the terminal with structured parsing |
| Notepad4 | Open source | 2017 | 5.1k star | Lightweight Windows Notepad replacement |
| Zed | Open source | 2021 | 95k star | The full editor from the GPUI team, already supporting Windows |
| Lapce | Open source | 2018 | 39k star | A mature native Rust editor |

Where users come from

- **Verified** **star farm** : GH Archive sampled 7 WatchEvents (11-17 19:39 through 11-18 18:15). Of these, 6 came from accounts registered between 2026-06 and November, with 0 followers and auto-generated usernames (-lang/-beep/-code/-stack); 1 have already been deleted. Their starred lists overlap heavily (mdiri-ai/SoduWork, beenuar/AiSOC, loysger/Antigravity, Check-Risk-WAF, npmscan, a cluster of *-osint-* repos). 11-19 SoduWork +1135, Antigravity +200, Check-Risk-WAF +129, the same day RustText gained +520. RustText's fork/star ratio is only 0.3%, with 39 downloads.

- **Verified** **Chinese GitHub star-trend aggregators** : mfy-lifeline.com/code, guoshiqi.xyz, and tgmeng.com list it #32 on the new-repo weekly board. They add repos automatically based on star growth, so they reflect the stars rather than explain them.

- **Verified** **The author's Russian-speaking circle** : two real Russian accounts, mergen1212 and TheVSAKeeper, opened PRs and forked the repo, which explains only a single-digit number of stars.

- Inferred **HN / Reddit / X / Habr / media** : HN Algolia, Reddit, x-radar over 30 days, and a Jina search of Habr all returned no matches.

## Illson/RustText: how it got 3+ stars in 600 days

> Query time 2026-11-19 (UTC). The 「today 2026-11-07」 in why.md is older than the data card, so the data card and live GitHub numbers take precedence.

### Bottom line first

RustText is a text editor and large-log viewer for Windows, built by a Russian developer for personal use (Rust + GPUI Kit), developed with a Codex-style agent pipeline. **It didn't take off organically: 600 most of its stars look bought.**

- Of the 7 stargazer accounts we could sample, 6 are star-farm accounts: registered less than six months ago, 0 followers, 0 repos, with usernames auto-generated by GitHub's suggestion pattern (ending in `-lang`, `-beep`, `-code`, `-stack`), and 1 of them have since been deleted by GitHub. They all starred the same set of repos.

- On the same day (11-19), this batch of accounts was also farming stars for mdiri-ai/SoduWork (+1135), loysger/Antigravity (+200), and Check-Risk-WAF (+129).

- Almost no usage: across 8 versions, RustText.zip has 39 downloads total; 1 watchers (the author himself); 2 forks, both by the author's two Russian coworkers.

- No discussion outside GitHub: HN, Reddit, X and Habr return nothing. Only Chinese trending-repo aggregator sites picked it up automatically.

### 1. What it is

- The README is in Russian and describes it as a "Windows x64 text editor and large log viewer, Rust + GPUI Kit." Features include tabs and session restore, the last 100 closed tabs, draft persistence, paginated viewing of large files, encoding and line-ending display, JSON inspection, single-instance forwarding, and an auto-updater. The README runs about 24 KB and is very detailed. (GitHub README)

- The repo was created 2026-11-16 17:46 UTC. The first 3 commits were pushed in one burst (17:32–17:44). As of 11-19 there are 41 commits and 8 releases (v0.1.0 to v0.2.2), with issue and PR numbers up to #55.

- Development runs on an AI agent pipeline. The repo's `AGENTS.md` requires each task to get its own worktree, branches named `codex/<task>`, PRs filled in from a template, and CI to pass before each PR. PR bodies follow a "Цель / Связь с issues / Изменения" (Goal / Related issues / Changes) structure, and reviews are formatted reports posted from the author's account. Issues are casual requirement notes written by the author, some with profanity; for example, #11 "адд" lists 13 ideas underneath. #50 and #51 have started rewriting the whole project as a single-EXE .NET 11 + Avalonia version.

- The author, Illson: account registered 2019 years ago, 0 followers, and of his 8 public repos, 7 are forks (scraping and automation libraries like BotBrowser, FlaUI, Leaf.xNet, Yove.Proxy). His only original projects are RDPForm (0 stars) and RustText.

- The two external contributors, mergen1212 (Tyuleev Mergen) and TheVSAKeeper (Савелий Вотинцев), are real Russian users whose accounts are 2022 years old, and they have submitted 5 PRs between them. They appear to be colleagues or friends of the author.

### 2. Growth data

| Timeline | star | Source |
|---|---|---|
| 2026-11-18 snapshot | 88 | our GitHub repo_day |
| 2026-11-19 snapshot | 608 (520 in a single day) | Same as above |
| 2026-11-19 03:40 UTC | 618 / fork 2 / watcher 1 | GitHub API |

- Downloads: the RustText.zip for each of the 8 releases has 5, 4, 4, 4, 8, 4, 4, and 6 downloads respectively, 39 in total; the sha256 files have 26 downloads, mostly CI or the updater verifying checksums. The ratio of stars to downloads is about 16:1. (GitHub Releases API)

- The fork-to-star ratio is only 0.3%. Compare repos created within ≤10 days that gained over 300 stars in a single day: erkamyaman/rust-anything 247/3092 (8%), Hut-hzf/ung220z-tool 269/1100 (24%), zephyr4123/snug 61/889 (7%). RustText is the lowest in this group, by an order of magnitude. (github repo_profile, 11-19)

### 3. Where the stars come from: a star farm (evidence)

GitHub's stargazers endpoint returned 404/403 for our token on every repo, including torvalds/linux, so we couldn't pull the full list. Instead we sampled GH Archive hourly events from 11-16 to 11-19 (GH Archive now only has about 4000 events per hour, so coverage is thin), and found 7 WatchEvents:

| Time (UTC) | Account | Registration date | Followers / repos | Verdict |
|---|---|---|---|---|
| 11-17 19:39 | Dobroezzhev1981 | 2026-08-16 | 0 / 0 | Farm accounts |
| 11-18 00:09 | brilliantnamira-lang | — | Since deleted by GitHub (404) | Farm accounts |
| 11-18 03:21 | chaesacorporate-beep | 2026-06-30 | 0 / 13 | Farm accounts |
| 11-18 05:23 | mahfuz6701 | 2026-06-17 | 1 / 0 | Suspicious |
| 11-18 05:58 | pjhulki60-code | 2026-10-06 | 0 / 13 | Farm accounts |
| 11-18 06:19 | ronu80691-stack | 2026-10-24 | 0 / 0 | Farm accounts |
| 11-18 18:15 | nzaleta | 2026-11-02 | 0 / 0 | Farm accounts |

The star lists of these accounts overlap heavily (GitHub API `users/<account>/starred`):

- Nearly all of them starred Illson/RustText, mdiri-ai/SoduWork, beenuar/AiSOC, loysger/Antigravity, Check-Risk-WAF/Check-Risk-WAF, NPMscan/npmscan-action, sleep3r/mtproto.zig, and tetiva-app/client.

- There's also a whole set of "*-osint-*" repos with the same template naming (StormBrawlerSack/legwork-osint-ai-investigator, SouthBowyerTug/gazette-osint-company-registries, CityGrubWedge/amber-osint-web-archive, etc.), and their author names look like random noun pairings.

- This batch of "customer repos" is also climbing the same day, and most of them have strangely few forks: Check-Risk-WAF 2278 stars / 10 forks, NPMscan/npmscan-action 510 / 1, loysger/Antigravity 1247 / 4, tetiva-app/client 320 / 1. 11-19 that day SoduWork +1135, Antigravity +200, Check-Risk-WAF +129, and they landed the same day as RustText's +520. (github repo_profile)

- Many of the client repos are from the Russian-speaking community (Oxotka/Landscape1C, fafnirov/KaproTUN, sleep3r/mtproto.zig, zxkill/homeassistant-is, seregonwar/PkgToolBox), which fits RustText's Russian background. Our guess is a star-selling service with Russian-speaking customers. Not verified.

One more timing detail: the farming began 11-17, the day after the repo was created and when the author shipped v0.1.x. Stars trickled in slowly until 88,11-18 to 19, then arrived in a batch of about 520. That matches a package that delivers in tranches so growth looks organic.

### 4. Competitors: who else does the same thing

| Product | Where | Launched | Scale | How RustText differs |
|---|---|---|---|---|
| Notepad++ | Open source / Windows | 2003(GitHub 2015) | 29.9k stars, the de facto standard replacement for Windows Notepad | Mature plugin ecosystem. RustText's pitch is "paginated large logs + session and draft recovery," and it has far fewer features overall |
| Windows Notepad (with tabs and session restore) | Big-company features | Added tabs and autosave in 2023 | Built into the system | RustText's tab restore and draft persistence for untitled files, which Notepad already has |
| Sublime Text / EmEditor | Commercial software | 2008 / 1997 | EmEditor, which focuses on opening multi-GB files | Opening very large files and split-pane layouts, which RustText lists as TODO issues and which these tools have had for years |
| klogg | Open source | 2016 | 3.6k star | A dedicated large-log viewer, cross-platform, with filtering and highlighting |
| LogExpert | Open source / Windows | 2017 | 1.2k star | tail and log analysis on Windows |
| lnav | Open source / terminal | 2009 | 10.8k star | Terminal log navigation with structured parsing |
| Notepad4 (Notepad2 fork) | Open source / Windows | 2017 | 5.1k star | Lightweight, fast |
| Zed | Open source (GPUI's own project) | 2021 | 95k stars, already supports Windows | A full editor on the same GPUI stack |
| Lapce | Open source / Rust | 2018 | 39k star | Native Rust editor |
| longbridge/gpui-kit | Open-source framework | 2024 | 21k star | The UI framework RustText itself is built on |

Data from the GitHub API, 2026-11-19.

This category has plenty of mature products, plus built-in features from big vendors. RustText has no differentiator worth noting. Its distinguishing traits are a Russian-language UI and a single person with an agent shipping several releases a day, and neither is a reason for a repo to earn many stars.

### 5. Checking for other growth sources

- Star farming: evidence in section 3. High confidence, but we only verified 6 of the 7 accounts we sampled.

- HN: an Algolia search for RustText returns no related posts.

- Reddit: nothing found. The only related r/rust thread is a general "editor written in Rust" discussion from 2023 years ago.

- X:x-radar, 30 posts in the last 0 days.

- Habr and Russian Telegram: no hits from Jina search.

- Chinese aggregator sites: mfy-lifeline.com/code, guoshiqi.xyz (GitHub trending projects), and tgmeng.com (ranked #32 on the new-repo star leaderboard for the past week, per the data card). These sites list repos automatically based on star growth, so they reflect the farming rather than causing it. That said, getting picked up by these leaderboards after buying stars is exactly the "visibility" a buyer is after.

- Media or big accounts: none.

### 6. Visibility and copycats

- Visibility: still low. Almost no one outside GitHub knows about it; the only pickup is automated leaderboards.

- Copycats: none. A niche Russian-language personal tool like this isn't going to be cloned.

### 7. Why the author might buy stars (speculation)

Public information shows no obvious commercial motive: no website, no paid tier, no hiring or resume links. Plausible guesses:

- To make a personal tool look used, to back up the auto-updater or the future .NET version;

- To pad a personal track record with a star count;

- To test a star-selling service.

None of the above is verified.

### 8. What's worth borrowing

The editor itself has nothing worth copying. Three things are worth noting:

- **How to spot it** : fork/star below 1%, downloads far below stars in releases, watchers at 1. Then pull a few WatchEvents from GH Archive to check account age and followers, and see which repos they all starred together. These steps can expose star-farming quickly. When we can't reach the stargazers API on GitHub, GH Archive sampling is a workable substitute.

- **The farm's shared client list** (SoduWork, Antigravity, Check-Risk-WAF, AiSOC, npmscan, a whole cluster of *-osint-* repos) can be used to apply a negative score to recommendations: new repos that surged on the same day as these get treated as suspected star-farming by default.

- **The one-person + agent open-source workflow** : AGENTS.md, PR templates, issue numbers in titles, CI treating Clippy warnings as errors. This setup is tidy, and it's worth studying how they organize their Codex pipeline. But it is not where the stars come from.

### 9. Uncertain

- We can't get the full stargazer list. GH Archive only sampled 7, so "almost all fake" is an inference, and the ratio is unverified.

- We don't know who bought the stars (the author or someone else), on which platform, or for how much.

- We don't know which hours between our 11-18 and 11-19 snapshots the stars actually landed in.

### Sources

- GitHub API: repos/Illson/RustText (and its commits, issues, pulls, releases, forks), users/Illson, users/<each starrer>, and users/<id>/starred

- GH Archive: hourly files from data.gharchive.org/2026-11-16-0 to 2026-11-19-2

- Our github library: repo_profile, repo_day(2026-11-19)

- Jina search: "Illson/RustText", RustText habr, RustText GPUI, etc.; HN Algolia; x-radar

- Aggregator sites: [mfy-lifeline.com/code/](https://mfy-lifeline.com/code/), [guoshiqi.xyz/](http://guoshiqi.xyz/); tgmeng.com from the data card

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.
