# 2254 stars, not a single off-platform discussion: How did a gRPC testing tool "go viral" · GitHub open source

> Source: https://stringers.io/en/github/gh_N4darae__shrt.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> It has not really spread: stars come in at a fixed 75–80 a day, with whole stretches at 0 followed by full restarts; the same author's other repo went to 2067 and then sat still for a month; the issues came from empty accounts registered in late August; almost nobody off-platform has mentioned it. The most likely explanation is that it was bought (inferred).

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

N4darae/shrt · N4darae

# 2254 stars, not a single off-platform discussion: How did a gRPC testing tool "go viral"

**What it is** A Go API regression testing tool: you write multi-step call chains in YAML, a human approves one run as the baseline, and every later release replays and diffs against it. It also ships a skill for AI coding agents.

**Why it took off** It didn't really spread. Stars came in at a steady 75–80 per day, a whole stretch flatlined for 0, then recovered. The same author's other repo reached 2067 and then sat still for a month. Issues came from empty accounts registered in August. Almost nobody off-platform mentioned it. The most likely explanation is inflated stars (inference).

**C** **How to ride it:** don't copy the gRPC version. Build the OpenAPI / REST version it's missing, or package "the agent runs tests, a human approves the baseline" as an agent skill any project can drop in in one line, and get real human stars via Show HN and a demo people can see working on the spot.

Grade C: the product design is worth learning from, but this niche has a low ceiling for organic spread (the closest competitor, Specmatic, has been around for 6 years and has only 401 stars). Later followers of shrt's 2000 stars won't get them, and buying stars gets penalized by GitHub. Hardly anyone knows about it yet

Data (updated daily) · Repo created 2026-09-03 · 2,460 stars · 7 days +479

GitHub · stars

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

N4darae/shrt is a Go API regression testing tool that collected 2254 stars in 64 days after creation. The idea isn't bad, but looking at its star curve, its issues, and the same author's other repo together, the stars look bought rather than spread organically. If you're trying to build a reputation through open source, what you can learn from it is product design, not the growth tactics.

### Six issues from Oct 21

On Oct 21, 2026, shrt's repo got 6 issues in one day. They came from three accounts, salzburghanging104, akiraokada-cloud and ismail-matar88, registered on Aug 24, Aug 24 and Aug 23. Each account has 0 repos and 0 followers. The issues are neatly written in standard bug-report format, and none of them has a single comment underneath.

By then the repo already had over 1200 stars (GitHub, as of 10-21 recorded at 1224). A project created only two months earlier, with the author having 54 followers and no Twitter, already looks like it has a "community." Looking back, how that "community" came about is fairly clear.

### What it actually is

shrt tests backend APIs. You write a call chain in YAML: log in → create a product → add stock → read it back. `shrt gate` runs every chain, and once they pass, a person must approve them with `shrt confirm -approve` before the result becomes the "baseline." Every later release replays against the baseline, and when a field changes, it points to the exact step and field, and suggests which write likely caused it.

A few design details are clever:

- A contract can include `effects: {qty_on_hand: {increase: qty}}`, meaning "after adding stock, stock should go up by qty." The tool automatically inserts a read before and after the write to verify this.

- It reads `.proto` files and guesses on its own which endpoint is login and which response field indicates success.

- `shrt init` also quietly installs a Claude Code skill. The README states: the agent can run the tests, but the baseline must be shown to a human, who has to nod before it's accepted.

The weaknesses are also clear: it only supports the Connect protocol (services written with connect-go), so pure grpc-go services won't work, and you still have to write the contracts yourself. The project description mentions "OpenAPI next," but it doesn't exist yet.

### The star curve doesn't look like organic growth

The daily numbers come from Trendshift. After 10-17, they match GitHub's daily counts:

| Timeline | New stars per day |
|---|---|
| 09-03 created → 09-28 | 0, a full 26 days |
| 09-29 | 6 |
| 09-30 → 10-05 | 80, 80, 77, 80, 77, 75 |
| 10-06 | 0 |
| 10-07, 10-08 | 158, 142 (looks like the previous day being backfilled) |
| 10-11 → 10-17 | 7 days in a row at essentially 0 (10-13 is 1) |
| From ¥10-18 | Back to 67, 75, 80, 55, 78, 65, 77, 75… |
| 11-01 | 0 |
| 11-05, 11-06 | 112, 105 |

Forks grow by 4 to 6 a day, a steady ratio of about 7% to stars; on the days stars hit 0, forks hit 0 too.

Open-source projects that really get discovered usually look like this: a spike when they hit the HN front page or a big account shares them, then a slow fall-off. shrt is a flat platform, with nearly fixed daily numbers, whole stretches that stop and then resume at the same speed. That fits the way star-boosting services work: deliver a fixed number per day, backfill if it's interrupted. **Inference** : GitHub doesn't publish shrt's stargazer list, so we can't check the accounts one by one. This call is based on the shape of the curve.

The same author also built another repo, anti-mage (Aug 22), which does anti-browser-fingerprinting detection. After it reached 2067 stars and 89 forks, it gained no stars for 29 days straight, from 10-09 to 11-06. A repo with over two thousand stars going flat for a whole month is rare; it looks more like a package that finished delivering. Its issues were also filed by a handful of random-looking accounts (zestycrane86, okonkwowren, lbarbosa81) between Sep 9 and 13.

There's another detail in the code: the top committer isn't the author. It's Kotaro with 2211,855 commits, an account registered in July 2025 with 1 followers; the author has 426 commits. The commits cluster on a few days, 9-28 (36 commits) and 10-02 (54 commits), with PR titles like "merge Lab round5". It looks like AI-generated code batch-imported in one go (inference).

### Who's talking about it: almost nobody

Neither repo shows up on HN; on X, searches for "N4darae" and "shrt grpc" over the past ~60 days return 0 results each; no media coverage, and no recommendations from real developers that we could find.

The searchable results are all auto-generated from star counts: ranking aggregators like Trendshift, gitranks, and hotrepo; pkg.go.dev auto-indexing; Instagram account @cloudedventures 10-28 posted "three AI coding libs everyone is starring this week," with shrt at #3 and marked ★1.8k; and an AI-generated YouTube Short (@NoShortAnswers, 10-27) with 1 views.

It sat in Trendshift's Go top 25 for over ten days, peaking at #5. That came from the star count, not the other way around, though it does pull in some real traffic as a side effect. 11-04 a contributor who looks like a real person appeared, idealistichacker (a student, 86 repos), opening 3 PRs that fix exactly the 10-21 issues. Whether they were drawn in by the star count or by the "easy-to-fix issues" is unclear.

### How big similar projects got

Plenty of projects do "API contract / regression testing" too. Stars in the 11-06 range:

| Project | Repo created | star | How shrt differs |
|---|---|---|---|
| Keploy | 2022-01 | 19.5k | Auto-generates tests and mocks by capturing real traffic; supports HTTP and gRPC |
| Schemathesis | 2019 | 3.7k | Property and fuzz testing driven by OpenAPI / GraphQL |
| Step CI / Karate | 2017–2022 | 1.9k / 9k | Declarative multi-step API testing, with no human-approved baseline |
| Pact(js / go) | 2016 | 1.8k / 960 | Consumer-driven contract testing; both sides have to integrate |
| Specmatic | 2020-03 | 401 | Turns specs into executable contracts, and also pitches "keep AI agents from drifting after code changes"; its positioning is the closest to shrt |
| Tracely-ai | 2026-10 | 1041, in the last ~7 days **-168** | Freezes an AI agent's production traces into regression cases |

Two numbers stand out. Specmatic, the project closest to shrt's positioning, has been around for 6 years with 401 stars: this niche grows through organic spread, and the ceiling sits roughly there. Tracely-ai appeared the same month as shrt and sells the same "regression testing for AI agents" pitch; it lost 168 stars in the last week, which looks a lot like GitHub cleaning out fake stars. Purchased stars can be taken back.

### If it were you

**C.** The product idea is worth borrowing; the growth playbook isn't. Anyone who wants stars from an open-source project should build a gRPC regression tool like shrt, but expect organic stars in the range of Specmatic's (hundreds), not two thousand.

**Who it suits** : people already writing backend code and wiring tools into AI coding agents, who want to build something they'd use daily and build a bit of reputation along the way. Especially people in the TypeScript / Python / OpenAPI ecosystem, which shrt doesn't cover, and where the "OpenAPI next" promise hasn't been delivered yet.

**Who it doesn't suit** : people who want stars to climb fast. The user base for this category is narrow, it requires writing contracts and committing to specific frameworks, so organic growth is slow. Buying stars gets them clawed back by GitHub, and once people notice, the reputation is worse than having no stars at all.

**How to build it** : don't copy the gRPC version; build the parts it doesn't cover. You could do an OpenAPI / REST version; you could generate the first contract version automatically from captured real traffic, skipping the hand-writing step; or you could package the "agent runs it, a human approves the baseline" workflow as an MCP server or agent skill that any project can plug in with one command. Three design ideas are worth borrowing: `effects` that automatically plan reads before and after writes, inferring login and success fields from the interface definition, and installing the agent skill during `init`.

**How to get users** : stars for this kind of tool come from real people's recommendations. Write a Show HN with a ten-minute demo that actually runs (shrt's README is a good model to copy); go where Claude Code and Cursor users gather and demo the moment "the agent broke an API and the tool caught it on the spot"; and answer questions like "how do I do regression testing for AI agents?" in the issues and discussions of projects like Keploy and Schemathesis.

**Why there's no rush** : the demand for test guardrails for AI agents is still early. Big-company frameworks (GitHub spec-kit, 148k stars) cover spec-driven development as a whole and haven't yet gone deep on API regression. Building this within six months isn't late.

**What would show this read was wrong** : ① after shrt or Tracely-ai, a real big account recommends it or HN discusses it, and star growth shifts from platform-driven to spiky, which would mean organic demand in this niche is bigger than estimated and worth moving on faster; ② an OpenAPI version of a similar tool gets over a thousand stars through organic spread within 3 months, meaning the gap is already taken; ③ shrt loses a large number of stars to GitHub cleanup over the next few weeks, which would confirm this piece's conclusion.

[GitHub repo ↗](https://github.com/N4darae/shrt)

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

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| Keploy | Open source | 2022-01 | 19.5k star | Auto-generates tests and mocks from captured real traffic; shrt plans call chains from contracts and has a human approve the baseline |
| Specmatic | Open source | 2020-03 | 401 stars, has a commercial version | Also pitches turning specs into executable contracts and preventing drift when AI agents change code; supports OpenAPI, while shrt currently only supports Connect/gRPC |
| Pact | Open source | 2016 | pact-js 1.8k / pact-go 960 star | Consumer-driven contract testing, both sides have to integrate; shrt only replays against the server side |
| Schemathesis | Open source | 2019-08 | 3.7k star | Property and fuzz testing built on specs, without multi-step state chains plus baseline diffs |
| Step CI / Karate / Hurl | Open source | 2017–2022 | Step CI 1.9k, Karate 9k stars | Declarative multi-step API testing, with no human-approved baseline, full-field diffs, or agent-facing skill |
| Bruno / Hoppscotch / Postman+Newman | Other | 2014–2022 | 48k / 81k / 7.3k star | General-purpose API client with collection testing; broad coverage, not aimed at agents |
| GitHub spec-kit | Big-company features | 2025-08 | 148k star | A general spec-driven development framework, not focused on API regression replay |

Where users come from

- Inference **Suspected purchased stars/forks (drip-fed daily)** : Trendshift day by day: roughly 75–80 stars a day, forks a constant ~7%; 10-06, 10-11~17, 11-01 all 0; after 26 days of existence and 0 stars, growth suddenly picks up; the same author's anti-mage sat at 2067 stars with zero growth for 29 days (our repo_day)

- Inference **Sock-puppet issues to fake community** : 10-21 on the same day, 6 issues from salzburghanging104, akiraokada-cloud, ismail-matar88, all accounts registered 2026-08-23/24, with 0 repos and 0 followers; anti-mage has issues from similar accounts too

- **Verified** **Trendshift, aggregators, IG/YouTube auto-content (passive)** : Trendshift Go Top 25 for over ten days (peak #5); @cloudedventures IG 10-28 post, @NoShortAnswers YouTube Short 10-27 (1 views)

- Inference **HN / X / media** : our hackernews and x-radar records show nothing in the past ~60 days

## N4darae/shrt: a gRPC regression testing tool with 2000 stars; the growth shape looks manufactured

> Channels: GitHub | Research day 2026-11-06 | Data sources: our github / hackernews / x records, GitHub API (2026-11-06, queried live), Trendshift, Jina/Exa web search

### Bottom line

shrt is a Go-based gRPC (Connect protocol) regression testing tool: multi-step API call chains are written in YAML, a run a human approves once becomes the baseline, and every later version is replayed and compared against it. It also ships a Claude Code skill. The product idea itself is solid. But **2254 stars and no outside source at all** : HN, X, Reddit big accounts, and media have never written about it. Stars started on day 26 (9-29), and from the start it was 75–80 a day, with forks at 5–6 a day, the same pace for a full month, with several stretches of exactly 0 in between. The same author's other repo, anti-mage, followed the same pattern: after reaching 2067 stars, it gained not one more in a month. The accounts that filed issues were all new, registered 8-23/24 with 0 repos, and the issues were filed together on the same day (10-21). **The most likely explanation is a 'drip-fed' star/fork package plus sock-puppet issues; this didn't grow through organic spread.** (This is inference; the stargazer list can't be checked, so it can't be verified directly.)

### 1. What it is

- README: call chains are written in YAML (login → create entry → add stock → read back). `shrt gate` runs the full chain, `shrt confirm -approve` has a human approve the baseline, and every later version replays and compares against it; when a field changes, it reports which step, which field, and which write may have caused it. `shrt init` also installs a Claude Code skill. It only supports the Connect protocol (connect-go services); pure grpc-go services aren't supported. The description mentions "OpenAPI next".

- Author Khanh (N4darae): account registered 2019 years ago, 54 followers, no Twitter, 4 public repos (GitHub API, 2026-11-06).

- Commit history: contributor Kotaro2211 has 855 commits (registered 2025-07, 1 followers), N4darae has 426 commits, hneastwood has 26 commits (registered 2026-10-02, 0 repos). Commits cluster on 09-28 (36 commits), 10-02 (54 commits), and 10-26 (9 commits), with PR titles like "merge Lab round5" and "Lean trace". It looks like AI-generated code batch-imported in one go.

### 2. Star curve: the shape doesn't look organic

Trendshift day-by-day data (https://trendshift.io/repositories/269536):

- Created 09-03, and through 09-28 it sat at 0 stars. 09-29 +6,09-30 starting +80, +80, +77, +80, +77, +75.

- 10-06 is 0; 10-07 +158,10-08 +142 (looks like the previous day being backfilled); 10-09 +106,10-10 +44.

- **10-11 through 10-17 was 7 straight days of 0** (10-13 +1). Starting 10-18 it went back to +67, +75, +80, +55, +78, +65, +77, +75...

- 11-01 is 0; 11-05 and 11-06 climbed to +112 and +105.

- Forks gained +4 to +6 a day, holding a steady ratio of about 7% to stars. On days with stars, forks rose; on days when stars were 0, forks were 0 too.

- Our repo_day data (10-17 to 11-06) checks out: 10-17→10-19 flat at 1002,11-01, then 11-02 flat at 1981; last 7 days +413, first 7 days +484; single-day peak +140 (10-20).

Organic breakouts usually look like this: an event (a Hacker News front page, a big account's repost) creates a spike, then a long tail decays. shrt's curve is a plateau at a fixed height, with whole stretches of zero followed by whole stretches of restarts, and the fork ratio never moves. That fits how star-boosting services deliver: a fixed amount per day, topped up on order. **The same author's anti-mage** (anti-fingerprint browser detection, created 2026-08-22): from 10-09 on we logged it every day, 2067 stars and 89 forks, and in 29 days it gained not one star. A repo with over two thousand stars that adds nothing for a month is rare. It looks more like a package that was delivered and then stopped.

### 3. Issues: a 'community feel' produced by sock puppets

- On 10-21, the repo got 6 issues from 3 accounts: salzburghanging104 (registered 2026-08-24), akiraokada-cloud (08-24), ismail-matar88 (08-23). All three have 0 repos and 0 followers. The issues share the same tidy bug-report style, and the comments all read 0.

- anti-mage is the same: from 09-09 to 09-13 it had 3 issues from zestycrane86, okonkwowren, and lbarbosa81, also accounts with random names.

- On 11-04, a contributor who looks real, idealistichacker (Jerry Yu, a student, 86 repos), opened 3 PRs fixing exactly the issues from 10-21. It could be a real person drawn in by the star count, or the 'easy-to-fix issues' may have lured them in.

### 4. Off-platform exposure

- HN: in our hackernews data, neither of N4darae's repos has ever been on HN (the only hit was an unrelated QRShrt).

- X: x-radar searches for 'N4darae', 'N4darae/shrt', and 'shrt grpc' returned 60 posts in the last 0 days.

- What web search turns up is downstream content that is auto-generated from the star count: aggregator sites like Trendshift, gitranks, hotrepo, GitRank, DiscoverGit, Git Homed, repolode, and gitofanton; pkg.go.dev auto-indexing; proskills.md listing its skill; a self-hosted panelalpha list; an Instagram account @cloudedventures (10-28, 'the three AI coding repos everyone is starring this week, #3 Shrt ★1.8k'); and a YouTube Shorts channel @NoShortAnswers (10-27, AI-generated, 1 views). A post on Reddit r/ArtificialInteligence, 'New agentic harness reads LESS source code…', has a title close to shrt's pitch, but the page is behind a captcha and I couldn't confirm its contents.

- Trendshift's Go Top 25 has carried it for a dozen-plus days (best rank #5). That is a result of the star count, not the cause, though it does bring a bit of real traffic. GitHub's official trending only admits repos about 60 days old, and shrt is 64 days old now and hasn't made it (our repo's trending_days_any=0).

Bottom line: **Almost nobody knows about it.** No real influencer or media outlet has spread it. The 'heat' we see is all generated by the star count itself.

### 5. Competitors (stars from our github repo data, 2026-11-06)

| Product | Form | Repo created | Scale | How shrt differs |
|---|---|---|---|---|
| Keploy | Open source | 2022-01 | 19.5k stars, +567 over the last 7 days | Auto-generates tests and mocks from captured real traffic, supports HTTP/gRPC. shrt plans call chains from contracts and requires a human to approve the baseline. |
| Specmatic | Open source + commercial | 2020-03 | 401 star | Turns OpenAPI/gRPC specs into executable contracts, and also pitches 'preventing drift after AI agents change code'. Its positioning is the closest to shrt. |
| Pact(pact-go / pact-js) | Open source | 2016 | 960 / 1.8k star | Consumer-driven contract testing, both sides have to integrate. shrt only replays against the server. |
| Schemathesis | Open source | 2019 | 3.7k star | Property-based and fuzz testing from OpenAPI/GraphQL. shrt does multi-step stateful chains plus baseline diffs. |
| Step CI / Hurl / Karate | Open source | 2017–2022 | 1.9k / not checked / 9k stars | Declarative multi-step API tests. No 'human-approved baseline + full field diff', and no design aimed at agents. |
| grpcurl / evans / ghz | Open source | 2017–2018 | 12.9k / 4.5k / 3.4k star | gRPC calls and load testing tool, no regression. |
| Bruno / Hoppscotch / Postman+Newman | Open source / commercial | 2014–2022 | 48k / 81k / 7.3k star | API client with collection testing, mature features from a big vendor. |
| Tracely-ai(jwuthri-cloud) | Open source | 2026-10-11 | 1041 stars, last 7 days **-168** | Freezes production traces from AI agents into regression cases. It sold 'regression testing for AI agents' in the same period, and its stars were recently removed (a sign of GitHub cleaning fake stars). |
| GitHub spec-kit | Big-vendor open source | 2025-08 | 148k star | A large spec-driven development framework with broader coverage. |

Differences shrt can actually state: (1) it targets only Connect/gRPC and infers the login endpoint and response conventions from the proto; (2) it plans read-before-write and read-after-write probe steps automatically from `effects` in the contract (e.g. 'inventory should increase by qty'); (3) baselines must be approved by a human, and the agent is required to show the table and wait for a nod; (4) `init` installs the Claude Code skill directly. These design choices are careful, but the user surface is narrow: you need connect-go and must write contracts yourself. These alone won't earn 2000+ stars. The closest in positioning, Specmatic, has been around for 6 years and has only 401 stars.

### 6. Growth tactics broken down

| Channel | Evidence | Confirmed? |
|---|---|---|
| Suspected purchased stars/forks (dripped daily) | About 75–80 stars per day, forks a constant ~7%; whole stretches of 0 with no stars; 26 stars within 0 days of creation, then a sudden surge; the same author's anti-mage went to 2067 and then stopped completely. | No (inferred; stargazer details not visible) |
| Sock-puppet issues to fake community | 3 empty accounts registered 08-23/24, 10-21 opened 6 issues on the same day; anti-mage used the same tactic. | No (highly suspicious) |
| Aggregator / Trendshift passive exposure | Trendshift Go Top 25 for a dozen-plus days; assorted repo aggregators; auto-generated 'trending repo' content on IG and YouTube. | Yes (a result of the star count) |
| HN / X / Reddit / media | Neither our HN nor X data shows it; a Reddit post wasn't confirmed. | Not found |

Where the money comes back: the open-source tool is free, the author has no homepage, no sponsor link, no Twitter. The star-buying may be for a resume, personal reputation, or to pre-hype a commercial product not yet public (anti-mage does anti-fingerprint detection, which is usually a risk-control or anti-fraud business). This part is unverified.

### 7. What others can learn

- The product design can be borrowed: 'agent runs tests, human approves baseline', 'write effects in the contract and auto-plan read-before/after-write', 'infer login endpoint and conventions from the proto', 'install the agent skill during init'. These are sound approaches to API regression in the AI coding agent era, and nobody has seriously done the OpenAPI version yet.

- On distribution there's a visible pattern: once a repo is pumped to 1–2k stars, Trendshift, assorted aggregators, and AI content accounts on IG/YouTube automatically repost it, forming a layer that looks like real heat. But the real reach of this downstream content is low (YouTube 1 views), and GitHub does clean up fake stars (Tracely-ai losing -7 stars in 168 days is an example), so the risk is real.

### 8. Still unclear

- The stargazer details can't be pulled from the GitHub API (GraphQL stargazers returns empty, REST returns 404), so we can't directly check the account creation dates and activity of those who starred. The star-buying is inferred from the curve and the issue accounts.

- Whether the Reddit post was written by the author and how much traction it got is unconfirmed.

- Whether any real users are using it is unclear. go install counts can't be retrieved; the only external contributor that looks real is idealistichacker from 11-04.

- What relation Kotaro2211 (855 commits) has to the author, and whether they're the same person, is unclear.

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