# Free queue-jumping help first, open source three days later: how a Google student verification script hit 1,775 stars in two days · GitHub open-source project

> Source: https://stringers.io/en/github/gh_JenkinWoo__sheeridVerify.html (Stringers / 什么值得做, generated 2026-11-21)
> 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

> The same week, LINUX DO saw a surge of zero-cost Google AI Pro access. Last year's student offer was up for re-verification, and a popular paid verification bot had just broken in mid-October. The author first verified people manually for free using forum accounts, 62 people queued, and three days later open-sourced it. The people in the queue became the first stars and forks.

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

JenkinWoo/sheeridVerify · JenkinWoo

# Free queue-jumping help first, open source three days later: how a Google student verification script hit 1,775 stars in two days

**What it is** A self-hosted web workbench that uses an anti-fingerprint browser to auto-fill the SheerID verification form for the Google student offer, with each task routed through its own proxy.

**Why it took off** The same week, LINUX DO kicked off a wave of getting Google AI Pro for free. Last year's student offer was up for re-verification, and the popular paid verification bots had just broken in mid-October. The author manually verified people for free using an old forum account, with 62 people queued up, then open-sourced it three days later. The people in the queue became the first batch of stars and forks.

**E** **How you could follow this** Don't build tools that get around verification. Borrow the playbook instead: in a community that knows you, first solve a legitimate problem for people for free, manually, when they're lining up for help. When you can't keep up, turn the process into a self-hostable tool and open-source it, then come back to the original thread and say so.

Grade E: the category is helping people get past eligibility checks, which carries contract-violation and legal risk. Similar repos have already been deleted, and one anti-fraud update would break them all. The stars came from a one-off freebie wave, and GitHub already has 126 similar repos, the largest with 3,500+ stars. Being talked about in small circles

Data (updated daily) · Repo created 2026-11-06 · 3,920 stars · 7 days +1,329

GitHub · stars

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

JenkinWoo/sheeridVerify is a tool that automatically runs SheerID student verification, and most people use it to claim the Google AI Pro student offer. Created Nov 6, and by Nov 8 it had 1,775 stars and 954 forks (GitHub, 11-08). The stars grew because three things landed in the same week, plus the author spent time in forums verifying people for free before open-sourcing, which built up a queue of people. The category itself is about getting around eligibility checks, so don't copy it. What's worth noting is the cold-start playbook.

### The Nov 3 afternoon post

At 2:42 Beijing time on Nov 3, 2026, a post appeared in LINUX DO's "Welfare & Deals" section titled "Help verify a few Google One student verifications for free." The poster, JenkinWoo, wrote just one line: "DM me the link, don't share it publicly, or it'll auto-expire after too many clicks."

Two minutes later came the first reply: "Thanks bro, link DM'd." In half an hour there were 30+ replies, nearly identical: "DM'd, thanks in advance bro" and "Messaged you, thanks a lot, I'll wait my turn politely." By evening people started explaining why they were in a rush: "My Pro just expired, can I still get in line? I can wait" and "Google just told me I need to verify this month." The author changed the title to "Please don't DM for now" and added: "Too many of you are sending requests. I'm handling them manually, so it's slow."

The thread ended with 1.5k views, 88 likes and 62 participants (LINUX DO, 11-08). Three days later, on Nov 6 at around 5:30 p.m., the author created sheeridVerify on GitHub with a single commit titled "Initial release." The same day, they added a line to the end of the original thread: "Now open source."

### What it is

A small web workbench you run on your own computer or server. Written in Node.js, built on Camoufox, an anti-fingerprinting Firefox. You queue a batch of verification tasks, each task can use its own proxy, and it opens the page, fills in the form, types with human-like timing, retries automatically when it hits "unable to confirm you are human," uploads documents, and waits for the result.

The README calls it "for teaching and research," and the repo doesn't include any code for forging documents; users have to supply their own. But what people want it for is clear: the only reply in a Meika forum thread discussing it was "looks dangerous."

### Where the stars came from

| Time (Beijing) | stars | fork | What happened |
|---|---|---|---|
| 11-03 14:42 | – | – | LINUX DO free verification-service post, 62 people in line |
| 11-06 17:28 | 0 | 0 | Repo created; 40 forks within the first hour |
| 11-06 | – | – | Original post updated with "Now open source," linking to an open-source promotion thread (that thread is now inaccessible); forwarded in a Meika forum post and an SEUS community post, 421 and 142 views |
| 11-07 | 458 | 326 | GitHub daily tracking; from the afternoon, English aggregator sites began indexing it (at 1.1k stars when Early Signal indexed it) |
| 11-08 | 1,615 | 882 | Single day +1,157 |
| 11-08 15:52 | 1,775 | 954 | GitHub, at time of scraping |

A few details:

- **Forks are more than half of stars (about 54%)** . For a typical repo people star to bookmark, forks run only 10–20% of stars. That suggests a lot of people are actually deploying it. Fork activity peaks between 11 and 1 a.m. and between 8 and 9 a.m. Beijing time, matching Chinese users' sleep and wake hours. I checked a dozen fork accounts, with sign-up years ranging from 2013 to 2026, and saw no sign of batches of fresh accounts padding the numbers.

- **The author isn't a public figure.** 31 GitHub followers, and his other repos have at most 90 stars. But he's an old account on LINUX DO, having made 33 posts and 275 replies, and people there trust him.

- **The repo was written to LINUX DO's rules.** The forum's "Open Source Promotion" tag requires full open-sourcing, a link crediting LINUX DO, and screenshots for AI-generated introductions. The repo includes a ready-made post draft, a "Community recognition and thanks" section in the README, and an AI-made introduction image, all matching those requirements. The cost of posting was close to zero.

- **Not on X, Hacker News, or ads** . X shows no discussion in the last 30 days, it never hit HN, and it didn't make GitHub Trending (repos under 60 days old can't make it). 11-07 at 11 PM it gained 92 forks in one hour; source not found, possibly forwarded from Telegram groups (inferred).

### Why this week

**The same week saw a wave of "free Google AI Pro" fever.** On Nov 4, a LINUX DO post titled "Google One free 24-month Gemini Pro membership (how-to) registration bot open-sourced" got 14.0k views and 688 likes. The two matching repos, worldonlyu/Google_AI_Pro_2Year_ZeroCost_Auto and mmdoctor/google-pro-helper, were created 11-04 and 11-05 with 3,133 and 1,173 stars respectively (GitHub, 11-08). sheeridVerify is the third in this wave to pass 1,000 stars, and it takes the student verification route. The three star curves have exactly the same shape.

**Last year's recipients were due for renewal.** Google's help page says student offers generally require re-verification through SheerID every 12 months. The line "My Pro just expired" in the thread refers to exactly this.

**The old route had just closed.** On October 18 and 19, users on NodeSeek reported that the commonly used Telegram verification bot returned "The student verification method for SheerID links is unavailable." One person got only 1 out of 5 people verified, and said "the bot is probably dead." Those bots charged per use, about $1.4 each. Later in October, a LINUX DO post said someone sold one verification for ¥700 (likely exaggerated, but it shows there's a price spread).

Demand was at a peak, the old supply had just been cut off, and the author already had a queue of people waiting. Releasing a free, self-hosted tool at that moment caught the entire gap.

### This category was already crowded

Searching "sheerid" on GitHub returns 126 repos (11-08). Some representatives:

| Project | Launched | Scale | How it differs |
|---|---|---|---|
| PastKing/tgbot-verify | 2025-12 | 3,578 stars / 1,072 forks | Telegram bot with points and redeem codes, designed as a paid service from the start, also auto-generating documents |
| ThanhNguyxn/SheerID-Verification-Tool | End of 2025 | Original repo 404 | A direct-API tool from a Vietnamese author, since deleted; only renamed mirrors remain |
| eztg/GPT_Sheerid_Auto | 2025-12 | 138 stars | A command-line tool leaning toward ChatGPT |
| coffeefreehans/google-one-verifier | 2026-10-20 | 5 stars | Same idea (browser automation), launched two weeks earlier, with no community backing; it didn't take off |
| Paid Telegram bots, account sellers, Xianyu manual verification | Always present | $1.4 to several hundred yuan per use | Shared exit IP; gets risk-controlled once many people use it |

Compared with these, sheeridVerify stands out in three ways: you can self-host it, each task uses its own proxy so you aren't crowded onto one exit with thousands of others; it uses a real browser to mimic human hands instead of forging API requests; and it has tests, CI, and deployment docs, where most repos in this category have one script and one screenshot. These explain why it was forked for use and why it outpaced coffeefreehans, which launched two weeks earlier. But what made it reach a thousand stars in two days was timing and those 62 people, not the code.

Copycats appeared right away: an hour and a half after creation, a same-name mirror, Nobody1118/sheeridVerify, appeared, followed by two more same-name repos, trendy31154 and Fardin-420.

### What's worth learning is the playbook, not the tool

Tools like this essentially help people who don't qualify get past eligibility checks, which carries terms-of-service and legal risk. Repos get deleted (ThanhNguyxn's is already gone), and Google and SheerID keep tightening anti-fraud measures, so everything breaks with the next update. Its stars came from a one-time freebie craze, and once the craze fades, so do the stars.

But its cold-start playbook works just as well for a legitimate project:

1. **Help people for free by hand first, then open-source.** A single post shows how many people want something (here, 62 people in line). On the day you open-source, the people in that thread are your first stars and forks. The author was also flooded with DMs himself; the tool grew out of "I can't handle this alone."

2. **Post in a community that trusts you, and write the repo to its rules.** An old account's credibility is worth more than any promotion. Putting the post draft, thanks, and intro image in the repo beforehand means you can post the day you open-source.

3. **Where a shared service is overloaded, "self-hosted" is itself the selling point.** When everyone shares one bot, one API, one exit, it breaks as soon as usage grows. A version anyone can run on their own machine naturally gets a high fork rate.

Another signal worth noting: Chinese developers have strong demand for cheaply getting AI subscriptions like Gemini and ChatGPT. In one week, three related repos each gained one to three thousand stars.

### If it were you

**E: Don't chase this category.** Another student-verification tool would get stars from a one-time freebie wave, and could be taken down, banned, or held accountable at any time. GitHub already has 126 similar projects, the largest with over 3,500 stars.

**Who it's for** : Nobody in this category. The play fits an open-source dev with an established account on a Chinese tech community (LINUX DO, V2EX, NodeSeek) who is willing to spend a few days helping people by hand first.

**Who it doesn't suit** : Anyone hoping to rack up stars with "freebie hunting" or "review-bypass" tools. Stars come fast and drop fast, and your reputation goes down with the project. People with no community credibility who just want to post and leave: coffeefreehans, which launched the same idea two weeks earlier, only got 5 stars.

**How to do it** : Find a legitimate thing people in forums are currently begging for help with: a shared service that's overloaded, an official tool that's hard to use, a setup everyone keeps getting wrong. Post and help people by hand for free to see how many are in line. When the queue is too long to handle, write up the manual process you used as a self-hostable tool and open-source it.

**How to get users** : Go back to that thread and add "Now open source"; write your thanks and intro image to the community's promotion rules; the people in line are your first users. After that, let English aggregators index it on their own; they only index projects that have already gained traction.

**When is "before" too late** : There's no deadline for the playbook. This category's window can close at any time: one anti-fraud update from Google or SheerID, or one takedown on GitHub.

**What would show I've misread this** : ① After 30 days, sheeridVerify is still up and hasn't been taken down, and it's getting issues and success reports, gaining several hundred stars a week. That would mean the demand lasts longer than a single freebie wave, and the call that "this category's window is short" was wrong. (The terms-of-service and legal risks don't change, though, so I still wouldn't recommend following it.) ② Google itself loosens student-offer verification, or cuts the AI Pro price so people don't need workarounds. Then this demand would shift to legitimate price-comparison and money-saving tools, and that's where it would be worth building.

[GitHub repo ↗](https://github.com/JenkinWoo/sheeridVerify)

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

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| PastKing/tgbot-verify | Open source | 2025-12-07 | 3,578★ / 1,072 fork | A Python Telegram bot with points and redeem codes, designed as a paid service, submitting through pure API calls and generating documents; sheeridVerify is a self-hosted browser workbench that does not generate documents in the repo |
| ThanhNguyxn/SheerID-Verification-Tool (and mirrors RivenLau/gem-doc, ilikejupiter/verif) | Open source | End of 2025 | Original repo 404; featured in 2026-02 on @pythontrending; mirrors 50–60★ | Direct API calls plus document generation; since deleted. sheeridVerify uses disclaimer wording and "doesn't generate documents" to reduce takedown risk |
| eztg/GPT_Sheerid_Auto | Open source | 2025-12-30 | 138★ | A command-line tool with TLS fingerprinting and proxy rotation, leaning toward ChatGPT, with no Web queue |
| bingofreedom/SheerID-Verification-Tool-Platinum | Open source | 2026-02-05 | 131★ | Command line, with typing simulation and noise injection; Indonesian circles |
| coffeefreehans/google-one-verifier | Open source | 2026-10-20 | 5★ | Also browser automation (DrissionPage), but with no community backing or credibility; it didn't take off |
| TG paid verification bots (gemin_sheerid_pass_bot, sheeridverify_bot, etc.) / 1key.me | Other | From ¥2025 | About $1.4 per use; broke down around 10-19 (NodeSeek) | Shared backend, easily overloaded or risk-controlled; sheeridVerify uses your own IP and proxies, and is free |
| Manual verification services / account sellers (lolz.team, TG, Xianyu) | Other | Always present | Someone quoted ¥700 each (LINUX DO 3072335) | Paid, done by hand; sheeridVerify is free and automated |
| worldonlyu/Google_AI_Pro_2Year_ZeroCost_Auto, mmdoctor/google-pro-helper | Open source | 2026-11-04 / 11-05 | 3,133★ / 1,173★ | Same LINUX DO freebie wave, taking the 24-month offer token / bulk registration route and bypassing SheerID; an alternative path |
| Google's official student offer + SheerID anti-fraud engine | Big-company features | Always present | Official | Legit eligibility checks; tools vs. the official side is a cat-and-mouse game |

Where users come from

- **Verified** **LINUX DO: free manual verification first, open-sourced later** : 11-03 The author posted "Help me verify a few Google One student verifications for free", 1.5k views, 88 likes, 62 people, 64 replies; 11-06 Later added "Now open source" with a link to topic 3133005 (currently can't be opened)

- **Verified** **LINUX DO "Open source promotion" compliance material** : the repo has docs/LINUX_DO_POST.md (a declaration template), a README credit to LINUX DO, and AI-generated intro images, which match the tag's mandatory requirements

- **Verified** **USCardForum and SEUS reposts** : USCardForum post 11-06 421 views ("looks sketchy"); SEUS post 11-06 142 views

- **Verified** **Aggregator / mirror sites** : Early Signal indexed it at 11-07 06:59 UTC (source "GitHub new"); also The Daily Commit, HDATF (four languages), HotRepo. All indexed after stars had already climbed

- Inferred **Telegram group or channel reposts** : 11-07 15 UTC, 92 forks in a single hour; source not found

- Inferred **X / HN / ads** : x-radar has 0 posts, none on hackernews, no ads seen

## JenkinWoo/sheeridVerify: why it hit 1.7K stars in two days

**In one line** : A local Node.js + Camoufox (anti-fingerprint Firefox) web workbench that turns SheerID student verification (mainly for claiming Google One / Google AI Pro student offers) into a task queue: each task can have its own proxy, it auto-fills forms, mimics human pacing, handles "confirm you're human" retries, uploads documents, and polls for results. The README frames it as "teaching and research".

**Takeaway** : It took off for three reasons. First, timing: in early 2026 November, a wave of "farming Google AI Pro" was sweeping LINUX DO; last year's student-offer users were hitting their 12-month re-verification; and the Telegram verification bots that worked in mid-October had just stopped working, leaving demand unmet. Second, the author had an established LINUX DO account: he first verified people manually for free, collected a pile of queued requests to validate demand, and open-sourced it three days later. Third, the product form: self-hosted, per-task proxies, anti-fingerprint browser, and solid engineering, which is why the fork rate reached about 54%. This is essentially a gray-area tool that bypasses eligibility checks, not a legitimate product to copy; what's worth remembering is its cold-start playbook and the demand behind it.

---

### 1. Data

| Timeline | star | fork | Source |
|---|---|---|---|
| 2026-11-06 09:28 UTC | Repo created | – | GitHub API (the repo has a single commit, "Initial release", 09:56) |
| 2026-11-07 | 458 | 326 | our GitHub repo_day |
| 2026-11-08 | 1,615 | 882 | Our github repo_day (single-day +1,157) |
| 2026-11-08 at time of crawl | 1,773 | 954 | GitHub API |

- fork/star ≈ 54%; ordinary bookmark-style projects usually sit at 10–20%, which suggests many people actually deployed it.

- Fork timing (GitHub forks API, UTC): 40 forks in the first hour after the repo was created; peaks clustered at 11-06 15–17 and 11-07 00–01 (late night and early morning Beijing time, 8–9 a.m.), and 11-07 15 hit 92 in a single hour. Overall it follows Chinese users' daily rhythm. I sampled 12 fork accounts: sign-up years range from 2013 to 2026, mostly Chinese developers with several repos, plus a batch-fork archive account like CrackerCat. No sign of new accounts being mass-created to inflate numbers. The stargazer list API returned empty, so star-level details aren't available.

- Author JenkinWoo: GitHub account created 2019, 31 followers, other repos include cloud-manager (90★), CardVerse (card-key delivery system, 38★), and web-tg-robot (Telegram admin bot). No prior notoriety.

- Zero issues (rare for a repo with 1.7K stars).

### 2. Where users came from (growth tactics)

**Main channel: LINUX DO, manual service first, open source later**

1. 2026-11-03 06:42 UTC, the author posted in LINUX DO's "Welfare" section: "Help me verify a few Google One student verifications for free," asking people to DM their SheerID verification links, which he ran manually. The post got 1.5k views, 88 likes, 62 participants, and 64 replies, nearly all of them "sent via DM, politely queued"; the author then changed the title to "Please don't DM for now… I'm handling these manually, so it's a bit slow" (https://linux.do/t/topic/3114952). Replies in the thread like "Pro just dropped, can I still queue?" and "Google says I have to re-verify this month" suggest many of the people coming in were long-time users blocked by re-verification.

2. 2026-11-06, the author added a note to the post: "Now open source: Google One student verification, open-sourced," linking to [linux.do/t/topic/3133005](https://linux.do/t/topic/3133005) (Exa index date 11-06). The post now shows "does not exist or is private". Whether it was deleted, hidden, or restricted by reading level is **unconfirmed** .

3. The author's LINUX DO account is an old one (avatar ID 22821, 33 topics created, 275 replies), so it has credibility; this isn't a new account pushing hard.

4. The `docs/LINUX_DO_POST.md`, the README's "Community recognition and thanks" section, and the AI-generated intro images are really about meeting LINUX DO's "Open source promotion" tag requirements: the project must be fully open source, must credit LINUX DO with a link, and AI-generated intros must be shown as screenshots (rules at [linux.do/t/topic/1776670](https://linux.do/t/topic/1776670); other posts under the same tag use the same declaration template, e.g. [linux.do/t/topic/3007075](https://linux.do/t/topic/3007075)). So the draft post was less about chasing stars and more about promoting in line with community rules.

**Secondary spread (all small-scale)**

- USCardForum 2026-11-06 "GitHub SheerID student verification, this is open source?": 421 views, the only reply was "looks sketchy" (https://www.uscardforum.com/t/topic/545007).

- SEUS community 2026-11-06 "Automated scripts that break student verification on every major platform are out": 142 views (https://s.eus/zh/post/2690772952639044794).

- Automatic aggregator sites: Early Signal first indexed it at 11-07 06:59 UTC, when it had 1.1k stars, headline "SheerID verification workflow sandbox gains 1k stars," source listed as "GitHub new" (https://earlysignal.news/s/jenkinwoo-sheeridverify); also The Daily Commit, HDATF (Chinese, English, Japanese, Korean), and HotRepo. These were indexed only after stars had risen, so they are a result, not a cause.

- Not found: searching our x-radar corpus for sheeridVerify / SheerID over the past 30 days returns 0 posts; it did not reach HN or trending (the repo was under 60 days old); no ads. The source of the 11-07 15 burst of 92 forks is **not found** , possibly Telegram channel or group reposts.

### 3. Why now

- **The same-week Google AI Pro freeloading wave** : LINUX DO 11-04 "Google One free 24 months of Gemini Pro membership (how-to post), registration bot now open source," 14.0k views, 688 likes, 314 people (https://linux.do/t/topic/3123997,2026-11-04, 19:48 UTC); corresponding repos worldonlyu/Google_AI_Pro_2Year_ZeroCost_Auto (created 11-04, 3,133★) and mmdoctor/google-pro-helper (created 11-05, 1,173★, whose README says "the original LINUX DO post is here"). sheeridVerify is the third to pass a thousand stars in this wave, but it took a different route: student verification. The three star curves share the same shape (from our github repo data: worldonlyu 11-05 285 → 11-06 2,185; mmdoctor 11-06 91 → 11-07 813).

- **Re-verification due** : Google's official notice says student offers generally require re-verification through SheerID every 12 months (https://support.google.com/googleone/answer/17422238). Users from the end of 2025 were coming due at that point; in August, a USCardForum post titled "Google Gemini offers another year of free student membership" said you "have to upload proof, verify with SheerID" (https://www.uscardforum.com/t/topic/526178). One Chinese tutorial claims this round of claims ends on 2026-12-31 (Sohu, unverified).

- **The supply got cut off** : Two NodeSeek threads, from 10-18 to 10-19, say the usual Telegram verification bot now returns "The Student Verification method using SheerID links is currently unavailable, please send /pixel." One person got only 1 out of 5 verified, and "the bot is basically dead." The thread also mentions pay-per-use at about $1.4 a go, paid in crypto via Binance (https://www.nodeseek.com/post-992459-1 , [www.nodeseek.com/post-993692-1](https://www.nodeseek.com/post-993692-1)). On LINUX DO 10-25, a post claims someone sold Gemini student verification for ¥700 each (likely exaggerated, but it shows the price gap, [linux.do/t/topic/3072335](https://linux.do/t/topic/3072335)). A free, self-hostable tool launched right when demand was looking for a new home.

### 4. Competitors

| Name | Where | Launched | Scale | Differences from sheeridVerify |
|---|---|---|---|---|
| PastKing/tgbot-verify | Open source | 2025-12-07 | 3,578★ / 1,072 forks (first posted in LINUX DO's resource roundup) | A Python Telegram bot with points, check-ins, referrals, and card keys, designed from the start as a paid service; it auto-generates documents and submits via pure API calls. sheeridVerify is a self-hosted browser workbench and does not generate documents in the repo. |
| ThanhNguyxn/SheerID-Verification-Tool | Open source | late 2025 – early 2026 | Deleted (404); featured on @pythontrending in 2026-02, with many forks and renamed mirrors (RivenLau/gem-doc 59★, ilikejupiter/verif 54★) | A Vietnamese author's direct-API tool that generates documents; since taken down, showing these repos do get removed |
| eztg/GPT_Sheerid_Auto | Open source | 2025-12-30 | 138★ | TLS fingerprint emulation plus proxy rotation, leaning toward ChatGPT, command line |
| bingofreedom/SheerID-Verification-Tool-Platinum | Open source | 2026-02-05 | 131★ | Typing mimicry and noise injection, command line, Indonesian circles |
| Hao-Monster/…mix-tgbot-verify, YiFanL0409/Gemini_Verification_Tool, zhaikong/sheerid-verification, smilegookey/SheerID_Doc_Generator, and others | Open source | From ¥2025-08 | Each 20–60★ | Mostly blends or forks of the two above, or document generators; weak engineering and docs |
| coffeefreehans/google-one-verifier | Open source | 2026-10-20 | 5★ | Same idea (DrissionPage browser automation), but no community backing; didn't take off |
| Paid Telegram bots (gemin_sheerid_pass_bot, sheeridverify_bot, etc.), 1key.me | Other | From ¥2025 | Charged per use, about 1.4 USD; briefly stopped working in mid-October | Shared server-side service that goes down once overloaded or flagged by risk controls; sheeridVerify uses your own IP and proxies |
| Manual verification services / account sellers (lolz.team, Xianyu, Telegram) | Other | Always present | Prices range from double digits up to "700 yuan" | Take money, do it by hand |
| Pixel offers, Jio 18 months, 24-month offer token injection (worldonlyu, mmdoctor) | Others / open source | 2026 | The last two each have 1–3K★ | A different route to AI Pro that bypasses SheerID; an alternative |
| Google's official student offer + SheerID anti-fraud engine (IVE) | Big-company features | Always present | – | Legitimate route; SheerID keeps strengthening its risk controls, so tools vs. the official side is a cat-and-mouse game |

### 5. Differentiation, and whether that's why it took off

1. **A workspace you can self-host and run concurrently, not a shared bot** : It has a task queue and concurrency limits, each task can have its own proxy (HTTP/SOCKS5), and it includes HTTPS for server deployment and systemd templates. Users run it on their own residential IP or proxy, so they don't get rate-limited by sharing one exit with thousands of others. It also suits people who verify accounts for others at volume. The author did manual verifications himself until his DMs were flooded, and the tool grew out of that situation. (11-03)

2. **Drives a real browser through the form instead of forging API requests** : it uses Camoufox with randomized typing and field delays, waits for controls to stabilize, automatically retries up to 3 times when it hits "unable to confirm you're human," and builds school emails as "firstname.lastname@school-domain". That targets SheerID's increasingly strict bot detection head-on.

3. **"Doesn't generate documents" plus a pile of disclaimers** : the repo contains no code that fabricates documents. Users supply local files or URLs (the name is passed as a `name` parameter in the download URL to fetch "the original file for this person"). This makes the repo look "cleaner" than competitors and may make it less likely to get taken down (ThanhNguyxn's earlier repo is already gone). But the post titles and the community read it plainly: it's "automatic verification," and it looks shady.

4. **Engineering quality** : it has tests (9 test files), CI on Node 22/24, deployment docs, and detailed error codes and state machine notes. In this niche, most repos are a single script and a screenshot, so this is unusual.

**Is that why it took off?** Only partly. The deciding factors were timing (the free-Gemini-Pro wave, re-verification deadlines, and bots going offline) and LINUX DO's old accounts validating demand first using a free service. The differentiation explains why it got forked for self-hosting rather than just starred and left, and why it beat coffeefreehans (5★), which had the same idea in the same period. On raw scale, it still hasn't passed PastKing's bot, which has 3.5K stars.

### 6. Visibility and copycats

- Visibility: **spreading within small circles** . It's been shared across Chinese deal-hunting and tech communities like LINUX DO, NodeSeek, Meika forum, and SEUS, plus automated aggregator sites. No media coverage, x-radar didn't pick up X discussion, and it wasn't on HN. It's free and has no publicly reported revenue.

- Copycats: there are already mirrors with the same name, Nobody1118/sheeridVerify (11-06 10:56, created 1.5 hours after the first repo), trendy31154/sheeridVerify (11-07), and Fardin-420/sheeridVerify; there's also marwanainaili2307-web/sheerid-recon (11-07, self-described as a "security reconnaissance record"), and 954 forks. The category was already crowded (searching GitHub for sheerid returns 126 repos).

### 7. What's worth borrowing (the playbook only, not the category)

- **Test demand in the community with a free manual service before open-sourcing** : one post shows how many people want it (here, 62 people in the queue), and those people become the first stars and forks when you open-source.

- **Write the repo to the community's promotion rules** : on LINUX DO, the "open-source promotion" tag requires crediting the community and posting AI content screenshots. Put the post draft and intro images in the repo so posting costs almost nothing.

- **In a category where shared bots get swamped and flagged, "self-hosted + your own exit IP" is the selling point itself** .

- Demand signal: Chinese users have huge demand for cheap access to AI subscriptions like Gemini and ChatGPT, and three related repos each picked up 1–3K stars in one week. But the student-verification route is essentially obtaining eligibility benefits through deception. It carries contract and legal risk, can be shut down at any time by Google or SheerID, and can get taken down by GitHub. **Not recommended to build, and not recommended to follow** .

### 8. Still unclear

- Actual success rate (there are no issues and no user feedback to go on).

- Why the LINUX DO open-source post 3133005 can't be opened now (deleted, hidden, or restricted by trust level), and its view count is unknown.

- The breakdown of where the stars came from (stargazer details aren't available), and where the 92 forks during the 11-07 15 wave came from.

- Where the documents come from: the repo supports pulling documents from a URL by name. Whether an external document-generation service sits behind that is unverified.

- Whether GitHub takes it down, and whether SheerID specifically blocks it.

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