500 stars for a code graph: it beat four top rivals on benchmarks, yet has only a fraction of their stars
What it is An open-source tool that builds your codebase into a "who calls whom" graph, so coding agents like Claude Code, Codex and Cursor can check what a change will affect and which tests to run before editing code.
Why it blew up It didn't really: about 500 stars came from a 10-point Show HN, Reddit self-promotion, automatic listing in plugin directories, a likely paid Trendshift promotion slot, and two batches of bot-account forks. Cumulative npm downloads are only around 4,100.
CHow you could follow it Stop building generic code graphs. Pick a language or scenario where name-matching is error-prone (Go, Rust, C++, monorepos), learn from its approach of using the compiler as the referee, benchmark against top rivals with public charts, ship under MIT with a one-line install, then post a comparison video on X and Reddit.
- Data (updated daily) · Repo created 2026-08-22 · 518 stars · 7 days +113
GitHub · stars Data 2026-10-14 → 2026-11-08 (26 days, 26 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
AxiomCode Graph builds a "who calls whom" graph of your codebase for coding agents like Claude Code, Codex and Cursor to query. In its own tests, it beat four rivals with tens of thousands to over a hundred thousand stars each. But after 76 days of being built, it has only about 500 stars, some of which were bought. If you want to launch an open-source project for stars in the "code graphs for AI agents" category, it's a good cautionary tale: a technically better tool can't earn stars in a late, crowded category.
A 10-point Show HN, and a question that went unanswered
In 2026 Oct 14 16:36 (UTC), team member HaoleiZ posted "Show HN: AxiomCode Graph, Reducing coding agent rework with formal methods" on Hacker News. 16 minutes later, the first reply came in, reading only "Formal verification code graphs are the need of the hour." The poster, spaliwal26, is someone on the team.
The thread ended at 10 points and 8 comments. There was only one real external question, from user math93: "Where do you use formal methods? How is it different from other code graphs for agents?" HaoleiZ's answer is the most valuable line of the project: most rivals rely on tree-sitter, heuristic rules or string search, whereas they use Datalog-style rule derivation. On the Defects4J benchmark they reached 94.9% accuracy, versus 48.7% for Graphify.
That day it had 110 stars. By Nov 6 it was at 507 stars (GitHub, 11-06).
What it is
You hand it a repo, and it computes for every function "who calls it and what it calls", stored as a graph. Before changing code, an agent checks the graph to see which methods a change will ripple into and which tests to run, without repeated grepping, which also saves tokens.
What sets it apart from peers is how it wires the links. Most code graphs parse syntax with tree-sitter, so when they see save() they look up any function named save. AxiomCode works more like a compiler: it first checks the caller's type, then determines which save is actually being called. The README explains up front why this matters: choosing tests means walking the call chain back several hops, and one wrong link drops every test downstream.
The install covers nearly every mainstream agent: an npm package @axiomcode/code-graph with a CLI and MCP server, plus plugins for Claude Code, Codex, Copilot, Gemini, Cursor, Windsurf and Devin. Java, TypeScript and Python are officially supported, JavaScript and C# are beta.
Behind it is a company, AxiomCode Inc. Its site says the graph "provides structured code context for AxiomEngine," and the next step is turning engineering specs into formal rules to verify the code agents change. So the open-source library is a lead magnet for a commercial product. The license is FSL-1.1-Apache-2.0: source is public, but for two years you can't use it to build a competing product. Strictly speaking, that's not open source.
Benchmark: it uses the compiler as referee
The best thing this project does is pick a scoring method nobody can argue with.
| On 748 real bugs from Defects4J, the share of all "bug-revealing tests" that the selected tests cover | |
|---|---|
| AxiomCode | 94.9% |
| GitNexus (48k stars) | 61.5% |
| codegraph (77k stars) | 52.3% |
| Graphify (143k stars) | 48.7% |
| grep by name only | 46.8% |
| code-review-graph (33k stars) | 21.9% |
Data is from its README; star counts are from GitHub as of 11-06. In another test, it uses Java bytecode and the TypeScript type checker as ground truth and checks whether each call edge is correct: on TS it scores 88.8%, codegraph 65.4%.
This is the project's own benchmark, but the method is public, the referee is the compiler, and the projects it names are all top players, which is rare in this category. The missing one is Serena (31k stars): it uses LSP language servers, which already carry type information, so its technical approach is the closest, yet it's absent from the table.
Where the stars came from
No single moment made it take off. The sources I could find:
- Show HN (10-14): 10 points. From that day, it gained 8 to 26 stars a day.
- Trendshift promoted slot: the tech blog Fervor AI 10-20 wrote that it "appeared this week in a promoted featured slot on Trendshift." Trendshift ads are charged per click, $0.70 each, with a $100 minimum. From 10-15 to 10-22 its daily gains held steady at 15 to 25 stars, and the timing lines up, so it was probably paid (my inference; I didn't see any ad record).
- Reddit self-promotion: a post on r/coolgithubprojects titled "I built an open-source code graph for Claude Code…" exists, but I couldn't find its score or comments.
- Automatic listings: sites like skillsdirectory.com, claudepluginhub.com, githubsignals.io and hnshowcase.com auto-scrape GitHub and generate pages, plus several AI-rewritten news sites, one of which even got wrong what the project does. No independent big account or outlet has written about it, and searching X for the past 90 days turns up no one mentioning it.
Some of it is fake:
- Between 10-28 03:49 and 05:23 (UTC), 56 new forks showed up, about one a minute. The account names look like VicentaKoelp, Cletus1Pagac, Evie5Kilback, the kind of names a fake-data generator makes. The few we spot-checked all signed up in late June, have dozens of public repos, and 0 followers. Stars went up by 81 that day and dropped by 44 the next, which looks like GitHub purged the fake accounts and took the stars back.
- 10-07 had 12 forks in a row within six minutes, with account names carrying suffixes like -cmd, -glitch and -ai that are common among bulk-created accounts.
Whether the team did it themselves or a boosting service used a new popular repo to age accounts on the side, there's no way to tell from outside.
Real use is also thin. From Sep 20 to Nov 5, npm recorded 4,102 cumulative downloads (public npm data), with peaks on release days and ten to twenty a day otherwise. Of the 69 open issues, most were opened by the core developers. The only HN comment that reads like user feedback says "tried it on my 80k-line TS project, performance is about the same as other graphs, call depth is a bit more accurate," and the poster's name is nearly identical to a contributor's.
Competition: a category that filled up in six months
"Give Claude Code / Codex a code graph and save tokens" was one of the hottest open-source categories of 2026:
| Project | Launched | Stars (11-06) | Approach |
|---|---|---|---|
| Graphify | 2026-04 | 142,885, +4,361 in the last 7 days | Builds a knowledge graph from code, docs, SQL and PDFs together |
| codegraph | 2026-01 | 76,773 | Pre-built tree-sitter index, auto-sync |
| GitNexus | 2025-08 | 48,288 | No server, runs in the browser |
| code-review-graph | 2026-02 | 32,607 | Leans toward code review |
| Serena | 2025-03 | 31,123 | LSP, has type information |
| code-graph-rag, CodeGraphContext, axon, roam-code and others | 2025–2026 | 0.5k–5.3k | tree-sitter + graph database + MCP |
| Graphicle | 2026-10-14 | 509 | Rust, code graph plus memory, appeared the same day |
Further up are GitHub's CodeQL and Sourcegraph, plus the grep, semantic indexing and LSP built into Claude Code and Cursor. Together they already meet most "find the callers" needs.
AxiomCode arrived 6 to 12 months behind the leaders, with about a three-hundredth of Graphify's stars.
Why it's more accurate but didn't get the stars
- This category gets stars from "one line to install, tokens saved right away." Precision only pays off on large Java/TS projects, when a change crosses several hops. A reader skimming the README can't feel that.
- The setup deters people: it needs Node 22.13 or later and Python too, and the FSL license instead of MIT makes some developers leave on sight.
- It doesn't plan to live on stars: it's the company's lead magnet, and what they actually sell is the formal verification that comes after. Stars matter much less to it.
- Distribution stopped at the cheapest steps: one Show HN, one Reddit post, one possibly paid ad slot, with no demo video on X and no one paid to write a review. The leaders got their traction from people sharing them on X and Reddit.
If it were you
Verdict: the "give agents a code graph" category is full, with the top players at hundreds of thousands of stars, and latecomers struggle to gather 500 stars in a month. Building another general code graph like AxiomCode's isn't worth it. What's worth copying is how it proves itself.
Who it suits: someone deep in one language's type system, compiler or static analysis, who can be clearly more accurate in a narrow scenario.
Who it doesn't suit: anyone trying to build a general graph that supports every language and every agent. Graphify and codegraph already occupy that ground, and you won't match their share count.
How to do it:
- Pick a narrow gap the leaders handle poorly: languages like Go, Rust, C++, Kotlin and Swift where tree-sitter name matching errs often, or scenarios like monorepos and cross-service calls.
- Copy its benchmark: use compiler or language server output as ground truth, name the top few rivals in a public benchmark (remember to include Serena), and make it a chart on the first screen of the README. That chart is your backing when people press you on HN.
- Installation should be one line, use an MIT or Apache license, and don't require extra runtimes.
How to get users: still do Show HN, but also record a 30-second comparison: the same change, the tests Graphify missed versus the ones yours selected, posted on X and r/ClaudeAI and r/LocalLLaMA. Submit the plugin to the Claude Code and Codex plugin marketplaces so the auto-listing sites pick up some long-tail traffic. Trendshift ads start at $100, so test one and watch conversions. Don't buy forks or stars: fake names adding a minute apart are obvious to anyone, and they get clawed back the next day.
Timing: the code indexing and LSP built into Claude Code and Cursor keep getting better. Once "find callers and pick tests" becomes a built-in agent feature, the room for third-party graphs shrinks. Move before the first half of 2027.
What would prove this read wrong: if AxiomCode climbs to several thousand stars on the strength of that benchmark chart, it would show that "more accurate" alone can earn stars, and you should then compete head-on on precision rather than hide in narrow languages. Conversely, if a leader like Graphify adds type resolution, the narrow gaps will get filled too.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one Graphify-Labs/graphify Open source 2026-04 142,885 stars, +4,361 in the last 7 days Graphify builds one knowledge graph from code, docs and PDFs and matches broadly by name; AxiomCode covers code only and aims for precision through type resolution (Defects4J 94.9% vs 48.7%) colbymchenry/codegraph Open source 2026-01 76,773 stars Pre-built tree-sitter index with auto-sync; AxiomCode is type-aware, TS call-chain edges 88.8% vs 65.4% abhigyanpatwari/GitNexus Open source 2025-08 48,288 stars Zero-server tree-sitter graph that runs in the browser; AxiomCode treats it as the toughest rival in its benchmark (61.5% vs 94.9%) tirth8205/code-review-graph Open source 2026-02 32,607 stars Local graph leaning toward code review; lowest score in the benchmark oraios/serena Open source 2025-03 31,123 stars Uses LSP, also with type information, and has the closest technical approach; AxiomCode's benchmark doesn't compare against it Graphicle-AI/graphicle Open source 2026-10-14 509 stars A Rust code graph with memory that appeared at the same time, similar in size GitHub CodeQL / Sourcegraph Big-company features Years CodeQL at 10k stars; Sourcegraph is a commercial product CodeQL also queries code in a Datalog style, but it's built for security scanning; AxiomCode packages the same idea as an agent plugin for impact analysis and test selection The grep, semantic indexing and LSP built into Claude Code and Cursor Big-company features 2025- All users The built-in tools are good enough for most "find the callers" needs; AxiomCode's pitch is more accurate multi-hop impact and test selection - Where users come from
- Verified Show HN: 2026-10-14 HaoleiZ posted a Show HN, 10 points, 8 comments, with team member spaliwal26 backing it up; stars have grown steadily every day since launch
- Inferred Trendshift promo slot (paid ad): Fervor AI's article 10-20 says it "appeared in a promoted featured slot on Trendshift this week." Trendshift ads cost $0.70/click with a $100 minimum. The 10-15 to 10-22 daily gain of +15 to 25 stars lines up with the ad window.
- Verified Reddit self-post: r/coolgithubprojects post "I built an open-source code graph for Claude Code would love your…". Score unknown.
- Verified Auto-indexed by plugin/skill directories and AI rewrite sites: pages exist on skillsdirectory.com, claudepluginhub.com, viralagent.si, githubsignals.io, hnshowcase.com, zicq.com and others.
- Verified Fake forks / fake stars: between 10-28 03:49 and 05:23 UTC, roughly 1 forks per minute, 56 forks in total, from accounts with Faker-generated names (VicentaKoelp, Cletus1Pagac, etc.) registered 2026-06,0 ago with followers; 10-07 six minutes saw 12 forks from -cmd/-glitch suffixed accounts; 10-28 +81 stars that day, −44 the next day
Why AxiomCode Graph (AxiomCodeAI/axiomcodegraph) took off
Research date 2026-11-06. Channel: GitHub. Data card: /home/ljr/fanout/why/cards/gh_AxiomCodeAI__axiomcodegraph.json
Bottom line
It never really took off. It's a late entrant in the already crowded "code knowledge graph for AI coding agents" space, with a technically distinct approach: call graphs built with type resolution and Datalog-style formal rules, where rivals use tree-sitter and guess by name. About 500 stars came from four places: a Show HN that scored 10 points, a Reddit self-promo, auto-scraped skill/plugin directories, and what may be a purchased Trendshift ad slot. The data also shows two batches of obvious bot forks, and GitHub reclaimed part of 10-28's star gains the next day. Real usage is small: about 4,100 npm downloads total since late September, mostly clustered on release days.
1. What it is
- Builds a codebase into a call graph (who calls whom, which methods and tests a change will affect), exposed to agents via a CLI, an MCP server, and plugins for Claude Code / Codex / Copilot / Gemini / Cursor / Windsurf / Devin. Java, TypeScript and Python are supported; JavaScript and C# are beta, plus HTML/CSS and XML/YAML config. (README: github.com/AxiomCodeAI/axiomcodegraph)
- The company is AxiomCode Inc. The license is FSL-1.1-Apache-2.0: source is visible, but commercial competing use is barred for two years, so it isn't strictly open source. The website axiomcode.ai says "AxiomCode Graph provides structured code context for AxiomEngine, enabling deeper formal verification." The next layer is translating engineering specs into formal rules to verify code agents change. The open-source library is clearly a funnel for the commercial product.
- Team: GitHub org registered 2026-08-20, repo created 08-22, v0.1.0 released 09-25 (launch article dated 09-24). Nearly all commits come from swapnilpaliwal-sd (1,948 commits, bio "Representing and building AxiomCode"). Other contributors include HaoleiZ / JaredHLZhang, rongzhichen, G6KlayWang, Whua689, suyashpaliwal26, all members of a small team. Source: GitHub API contributors.
II. Growth data
| Date | stars | Daily gain | fork | Source |
|---|---|---|---|---|
| 10-14 (Show HN day) | 110 | – | 14 | Our GitHub repo (deeply source) |
| 10-15 to 10-22 | 124→257 | 8–26 per day | 14→24 | Same as above |
| 10-23 to 10-27 | 262→315 | 1–30 per day | 23→28 | Same as above |
| 10-28 | 396 | +81 | 84(+56) | census |
| 10-29 | 352 | −44 | 86 | snap |
| 10-30 to 11-06 | 365→494 | 13–24 per day | 86→87 | snap |
- On day 11-06, the GitHub API showed 507 stars, 87 forks, 19 watchers. Over the last 7 days it gained 129, over the 7 days before that 103. The repo is 76 days old and never made trending (repos under 60 days can't make it anyway, so that proves nothing).
- npm
@axiomcode/code-graphcumulative downloads from 2026-09-20 to 11-05: 4,102. Peaks fall on release days: 10-25 177, 10-27 169, 10-29 306, 11-05 328. Most other days show only a dozen or two. (api.npmjs.org) - 69 open issues aren't evidence of active users. Of the last 100 issues/PRs, 31/36 issues and 58/64 PRs came from swapnilpaliwal-sd himself, and the rest are mostly team members and CI bots. The only external user feedback visible is one HN comment: "Tried it on my 80k-line TS project, performance is about the same as other graph tools, call depth is more accurate." That commenter is Whua33, most likely contributor Whua689.
Data quality: clear signs of paid acquisition and star-botting (verified)
- 10-28 batch of 56 forks: between 03:49 and 05:23 UTC, roughly one per minute. Every account name is a Faker-generated English name, e.g. VicentaKoelp, othawuckert, goldabergnaum, Cletus1Pagac, Eric2Smitham, Oda1Zieme, Evie5Kilback, Cordie6Wisoky, Willis18Hoppe, Albert368892Leffler, Reinhold24Waelchi. Spot-checking 5 of them: 4 were registered between 2026-06-21 and 06-25, each with dozens of public repos and 0 followers. Stars rose +81 that day and −44 the next, consistent with GitHub purging fake accounts and reclaiming their stars. (GitHub API /forks, /users)
- 10-07 batch of 12 forks: arrived back-to-back within six minutes between 05:15 and 05:21 UTC. Account names carry -cmd, -glitch, -cloud, -ai, -cyber, -del suffixes, e.g. alirezaalirezaalireza13711-cmd, sabakhansee33-glitch, nicolewilliams8994-ai, a common mark of batch-created accounts.
- The stargazer API returns 404 for both this repo and the comparison repos, so stargazers can't be checked individually. From 10-30 onward it gained a steady 13–24 stars per day. Whether that's organic growth or even, paced star-buying can't be determined (unverified).
3. Where users come from (growth levers)
- Show HN (verified): 2026-10-14 was posted by HaoleiZ, scoring 10 points with 8 comments. In the thread, team member spaliwal26 chimed in, and another user's feedback may also have come from a team member. (https://news.ycombinator.com/item?id=50090514) Star growth started that same day, adding a dozen to two dozen a day.
- Trendshift promo slot (likely paid): Fervor AI's article 10-20 says the project "appeared in a promoted featured slot on Trendshift this week." Trendshift sells native ads on its homepage feed and sidebar, priced per click at $0.70 with a $100 minimum, claiming 1,600–2,200 clicks a month. (https://fervorai.dev/articles/axiomcode-graph-gives-coding-agents-a-call-graph-instead-of-grep/ , trendshift.io/advertise) Stars rose steadily by 15–25 a day from 10-15 to 10-22, matching the ad window, but no placement records were found, so this is a strong inference only.
- Reddit self-post (exists, content not read): r/coolgithubprojects has a post titled "I built an open-source code graph for Claude Code would love your…". Reddit blocked scraping, so the score and comments are unknown.
- Auto-indexed long tail: many sites scrape GitHub and generate pages automatically, such as skillsdirectory.com (Grade A Claude Skill), claudepluginhub.com, viralagent.si, githubsignals.io, hnshowcase.com, linuxcommandlibrary.com, plus AI-rewritten news sites like zicq.com and mortaf3.com (the zicq article even gets the product wrong). All of this is passive exposure; none of it was written by a major independent author.
- Fake forks / fake stars (verified): see the previous section.
- Name piggybacking (more likely accidental): the name "Axiom" has been dominated by Axiom Math (valued at $2026B, doing formal proofs) in 1.6. Searching "AxiomCode" on X turns up only @axiommathai. Both companies pitch formal verification of AI-written code, so some spillover is possible, but no direct evidence of users confusing the two was found.
- X / TikTok / media: x-radar shows 90 mentions of "axiomcode" in the last 0 days, and Brave found no X major accounts mentioning it. No media coverage and no Product Hunt launch.
IV. Competitors (all checked in our GitHub repo; star counts are as of 2026-11-06)
| Product | Type | Launched | Scale | How AxiomCode differs |
|---|---|---|---|---|
| Graphify-Labs/graphify | Open source | 2026-04 | 142,885 stars, +4,361 in the last 7 days | Graphify turns code, docs, SQL and PDFs into a knowledge graph, with broad coverage. AxiomCode only does code call graphs but gets precision from type resolution; in its own benchmark, Defects4J test selection scores 94.9% vs 48.7% |
| colbymchenry/codegraph | Open source | 2026-01 | 76,773 stars, +901 | codegraph pre-builds an index with tree-sitter and syncs automatically, for Claude Code/Codex. AxiomCode's pitch is type awareness: TS call-chain linking 88.8% vs 65.4% |
| abhigyanpatwari/GitNexus | Open source | 2025-08 | 48,288 stars | GitNexus emphasizes no server, running in the browser. AxiomCode treats it as the "best tree-sitter rival" (61.5% vs 94.9%) |
| tirth8205/code-review-graph | Open source | 2026-02 | 32,607 stars | Leans toward code review; scores lowest in the benchmark (21.9%) |
| oraios/serena | Open source | 2025-03 | 31,123 stars | Serena uses LSP language servers and also has type information, making it the rival closest to AxiomCode's technical approach. AxiomCode's benchmark table does not compare against Serena |
| vitali87/code-graph-rag, CodeGraphContext, harshkedia177/axon, Cranot/roam-code | Open source | 2025–2026 | 0.5k–5.3k stars | All are tree-sitter or graph-database plus MCP, heavily overlapping in positioning |
| Graphicle-AI/graphicle | Open source | 2026-10-14 | 509 stars, +66 | Similar newcomers that appeared around the same time (Rust, code graph plus memory), about the same size as AxiomCode |
| github/codeql, Sourcegraph (SCIP/Amp) | Big-company features | Years | CodeQL at 10k stars; Sourcegraph is a commercial product | CodeQL also queries code in a Datalog style, but targets security scanning; Sourcegraph is a "code context layer for humans and agents." AxiomCode essentially turns CodeQL-style formal querying into an agent plugin |
| Claude Code / Cursor ship their own LSP and code indexing | Big-company features | 2025– | All users | The grep, semantic indexing and LSP built into agents already cover most "find the callers" needs. AxiomCode has to prove that multi-hop impact analysis and test selection beat these. |
The top handful of repos in this space each have tens of thousands to over 100K stars. AxiomCode entered 6 to 12 months late, so its star count is a fraction of theirs.
5. Why it didn't take off
- Timing: In 2026, "give Claude Code/Codex a code graph to save tokens" was already a hit category. Graphify is at 140k stars in half a year, and codegraph at 77k. AxiomCode rode the category's heat, and that heat is why people clicked through from its HN post and plugin directory listings.
- Product: The differentiation is real and testable. It scores itself against compiler output as ground truth (Java bytecode, the TS type checker), runs test selection on 4 bugs from Defects748J, and names four top competitors in its comparison. That's a rare hard benchmark in this category, and it's the only point HN pressed on.
- Distribution: No organic spike. The path was Show HN (10 points) → a Trendshift ad slot (likely paid) → Reddit self-promotion → automatic directory listings. Two batches of machine accounts also forked the repo, and some of those fake stars were later cleaned up. Growth ran at a dozen to twenty-some stars a day, about what a small paid ad buy would produce.
- Usage: About 4,100 cumulative npm downloads, clustered on release days. Almost no external issues. No evidence of a meaningful base of real users.
6. Is the differentiation why it worked?
There are three differentiators: type-aware analysis instead of tree-sitter name matching; Datalog-style rule inference with a deterministic label on every edge; and scoring against the compiler as ground truth. All three are real and checkable, and they hit the top competitors' weak spot: multi-hop call chains that break and lose everything. But this only earned it "how is this different?" questions on HN, not growth. Three reasons: first, the category rewards "install in one line, tokens saved right away," and precision only pays off on large Java/TS projects and multi-hop changes; second, the benchmark left out Serena, another competitor with type information; third, the FSL license and the Node 22 plus Python install requirements turned some people away. So the differentiation is not yet what's driving growth. It is the technical foundation for the enterprise product it plans to sell later (AxiomEngine formal verification).
7. Visibility and copycats
- Visibility: Almost nobody knows about it yet. No public revenue, no press coverage, 0 mentions on X, one Show HN at 10 points, plus a handful of auto-scraped sites and AI-rewritten sites.
- Copycats: None. The existing forks are team members and machine accounts.
VIII. What to take from it
- Entering a crowded category as a late arrival: pick a metric that can be scored objectively against a "ground truth," such as compiler output or Defects4J, name the top few competitors, and make it the first image on the README. It's a cheap way to build technical credibility.
- Package the engine as an npm package with one-click install through several agent plugin marketplaces, covering Claude Code, Codex, Copilot, Gemini, Cursor, Windsurf, and Devin at once, and pick up automatic listings in each vendor's plugin directory.
- Trendshift charges per click ($0.70, $100 minimum). It's a cheap channel for buying developer exposure for a new GitHub repo, and worth testing.
- The cautionary side: fork and star farming is easy to spot (fake names, one per minute, cleaned up the next day). For a company that plans to sell to enterprise customers, it's a liability.
9. What I'm still unsure about
- Whether the Trendshift promotion slot was bought by the team: the only source is one Fervor article. No placement records found.
- Were the 10-07 and 10-28 batches of forks farmed by the team itself, or by a third-party fake-star service (some of them pump trending new repos to age their accounts)? The accounts' fingerprints are certain; who placed the order is not.
- Stargazer-level detail can't be retrieved, so how many of the steady star gains after 10-30 come from real people is unverified.
- The Reddit post's score and comments are unknown. Team background and funding weren't found (LinkedIn has haolei-zhang, but it's behind a login wall).