Stringers
havenicec/google-qr-sms-helper · havenicec

A post with nothing but one link, and 75 stars in a day: how a small extension that bypasses Google's QR verification was found by people who were stuck

What it is A Chrome / Edge extension that helps users in China skip the step of logging into Google Antigravity and Cloud Shell where you scan a QR code and then send an overseas SMS from your phone. Instead, you enter a phone number and receive a verification code.

Why it blew up Google switched verification this year to scanning a QR code that sends an uplink SMS, which doesn't go through in China, so logging into Antigravity loops forever. A post in a 43 comment thread, a help issue unresolved for half a year, got passed along on nodeseek just as the mass-signup accounts farming Ultra 20x were getting hit by risk control on 11-17, adding +75 stars in a single day.

CHow you could follow this Find a pitfall on a major platform that just changed its rules and is stopping a large group of people, turn the manual workarounds from the community into a one-click tool, and place it in the issue and forum threads where the pain is concentrated. To stay in this niche, build a maintained version that keeps tracking Google's changes and supports more browsers.

Grade C: the playbook is clear and anyone can copy it, but this project depends on a Google loophole and a one-off wave of free-tier farming, reaching only a few hundred stars. The gap will get patched, and the issue section already reports it breaking, so following it directly isn't worth much. Circulating in small circles
Data (updated daily) · Repo created 2026-10-26 · 272 stars · 7 days +222
GitHub · stars
010020030011-0611-1011-1311-1611-20272
Data 2026-11-06 → 2026-11-20 (15 days, 15 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

google-qr-sms-helper is a browser extension with only 4 commits; the author published it and then left it alone. Its scope is very narrow: when signing into Google from desktop, Google asks you to scan a QR code and then send an SMS to Google from your phone, which users in China can't do. The extension swaps that step back to entering a phone number and receiving a 6-digit code. It was never listed in a store and was never promoted, yet in 23 days it collected more than 170 stars, all from people already stuck and searching everywhere for a fix. Below: what problem it solves, where the stars came from, who else is doing the same thing, and which steps to copy if you want your own open source project to take off the same way.

A post at 11:50 PM

On 2026 Nov 17 at around 11:50 Beijing time in the evening, a user named Seven posted on the Chinese hosting forum NodeSeek with the title "Seeing everyone grab 20x, here's a pretty handy tool to bypass anti-gravity devices for SMS". The post body was just one line and a link: "Use Google Cloud downgrade to bring back the traditional Google CAPTCHA", pointing to the repo.

The first reply came a minute later: "Good stuff, starred." The second: "Awesome, starred." The fourth threw cold water: "I think this doesn't work anymore, you still need to send SMS from your phone," and the OP replied "It works" and "Some of my accounts skip that step, you get past it, sometimes you need to refresh." The whole thread had fewer than ten replies.

On GitHub, though, within 4 minutes of the post (UTC 15:47–15:51), the repo gained 5 forks in a row. The star count went from 89 to 164 the next day, +75 in one day, and later that day reached 174 (GitHub, 11-18).

Why did a one-line post carry so much force? That day nodeseek and linux.do were both full of other posts teaching people how to get a free one-month or even one-year Gemini Ultra 20x with burner accounts, and the OPs kept warning "don't use your main account, use a burner." Once a burner claimed the offer and tried to log into Antigravity (Google's AI coding IDE launched this year, nicknamed "anti-gravity" in China), it was immediately flagged for verification. Another thread that day had someone on page two saying "Just farmed a month and the account got risk-controlled and needs SMS verification," and someone asking a seller whether there was a "7-day warranty, since so many people are getting verified." Seven's link landed right in the hands of the people most desperate that night.

What it solves: a trap Google built itself

From 2025 to 2026, Google changed verification for some accounts from "we send a code to you" to "you scan a QR code, then send us an SMS from your phone." For accounts with heavier risk controls, that's the only path left.

In China this step almost never works: most domestic phones lack the full Google services framework, and carriers block upstream SMS sent to overseas numbers. The result is an endless loop: you scan the code, the SMS won't send, you switch phones and scan again, and it still won't send.

Antigravity pushed this trap to its extreme. In an Antigravity account-management tool with 33k stars (lbjlaq/Antigravity-Manager), an issue opened on May 29 is titled "Antigravity asks for phone QR scan verification" and still open, with 43 comments. People tried Pixel phones, flashing GApps, iPhones with the Google App and YouTube for scanning, and Android emulators, with success rates ranging from "fairly high" to "unknown." In September someone wrote: "I've never used a reverse proxy or multi-account manager, and I still got risk-controlled just using it normally."

This extension turns "luck" into "one click." First you open Cloud Shell in the Google Cloud console, which pops up a Verify window, then you click the plugin's button on the QR page. It recognizes the QR code itself, calls Google's internal endpoints in the background, disguises the browser as an iPad Mini, and then takes you to the "choose verification method" page, where you check SMS, enter a number that can receive texts, and you're through. The README says that once you pass verification through Cloud Shell, the account is unlocked overall and you can log into Antigravity again.

The code is small: a Manifest V3 extension supporting Chrome, Edge, and Brave. You download the zip and load it manually in developer mode; it isn't in any store. Most of the README is a beginner-friendly, illustrated Chinese tutorial with a FAQ.

Where the stars came from: three paths that stuck people always end up on

TimelineWhereWhat happened
10-30The issue with the 43-comment threaduser li-ming1 left a comment saying "this project solved it for me" with a link, and 3 people liked it; 11-01 someone wrote up five workarounds and listed it too
Starting late OctoberChinese tech blogyyzmiao.top's "Google Antigravity login troubleshooting guide" has a whole section teaching this extension, with text nearly identical to the README
11-14XA long Chinese X thread, "Fully unlocking Google Antigravity × Gemini 4 bundle, hands-on tutorial", where step two is installing it (reach not verified)
NovemberRussian-language AI channelA "Зона ИИ" repost on VK / Telegram
Night 11-17nodeseekSeven's post, riding the wave of people farming the Ultra 20x promo

The curve matches too: it was at 11-06 stars, then gained +21 to +2 a day, reaching 8 by 11-16 and 69 stars, which is the long tail from issue replies and tutorials; 11-17 went to 89,11-18 with +75 in a single day (GitHub daily star count).

Two numbers show these stars didn't come from idle browsing. First, the zip in Releases was downloaded 919 times (GitHub, 11-18), more than 5 times the star count. Second, there are 38 forks, about a fifth of the stars, far above what a typical project gets. The people arriving actually needed it to get through verification.

One caveat: the blog post and the X thread both match the README almost word for word, and the blog author's GitHub account was only registered in early October. Whether these are the same person as the project author, or whether they were pushed together, can't be determined (inference: the author may have been seeding tutorials himself).

Who else does the same thing

WorkaroundWhat it isCompared with alternatives
Manual hacksScanning with a real phone's Google App / YouTube, spoofing the native Google framework, Pixel direct pass, luck with incognito modeMost widely used, but environment-dependent and unreliable
zicuharabim/QR-SMSA bookmarklet tool from 2026 February, same ideaAbout 3 stars; it's a bookmark with no automatic device spoofing, so more primitive
Paid verification bypass"Auto verification" on reseller sites: someone bypasses it for you when you orderYou pay and have to hand over your account
Bulk Gmail account creation toolse.g. ShadowHackrs/gmail-account-creator, about 5,900 starsBuilt for mass-producing accounts, not for "I can't log into this account I already have"
Official GoogleOnly offers "try again on a real device"No official downgrade path exists, and that's exactly the gap it fills

It outpaces similar tools for two reasons: the others are manual steps or bookmarks, while this one is one click; and the others are generic "Google verification" tools, while this one is tied to the hottest login scenario of this year, Antigravity. I haven't seen any renamed copy repos being pushed out, and most of the 38 forks look like personal backups.

Its weak spot: the author is gone and the extension is breaking

All 5 issues are from Chinese users: "still can't jump back to phone number verification" (11-08), "it works now. Awesome" (11-10), "what do I do if I can't log in" (11-10), "after clicking the cloud terminal, verify doesn't pop up" (11-16, with someone below replying "same problem here"), "has this route been blocked?" (11-18). The author hasn't replied to any of them, and the last commit was in October 28. Someone on the nodeseek thread also said "this browser or app may not be secure... can't get in."

It depends on internal Google interfaces that aren't public and on device-check rules. One change from Google could break everything. This surge was driven by a one-off freebie wave; once it fades, fewer people will search for it.

If it were you

In one line: this project isn't worth building again, but its path to stars is worth learning. Find a pain point on a major platform that has just been created and is still bleeding, and put a one-click fix in the thread where people are asking for help most. The scale is hundreds of stars, and the window is measured in weeks.

Who it suits: developers who understand browser extensions or reverse-engineer web flows, who move fast, who hang out in communities like linux.do, nodeseek and V2EX, and who can see first-hand where people get stuck.

Who it doesn't suit: people who want thousands or tens of thousands of stars, or who want to build something maintainable long-term (a tool like this lives or dies on whether the platform patches the hole). Also anyone uncomfortable with gray areas: its main users are burner accounts verified with SMS-receiving numbers, so account bans and repo reports are real possibilities.

How to do it, three ways to follow, from most to least confidence:

  1. Apply the same play to a different gap: watch for places where a major platform has just changed its rules and a lot of people are stuck (login verification, regional restrictions, mandatory device checks in new apps), and turn the manual hacks circulating in communities into a one-click tool. The test: does a big repo's issue or a forum thread have dozens of comments and months of no fix?
  2. What it does poorly: it requires detouring through Cloud Shell before returning to Antigravity, doesn't support Firefox, and the author doesn't respond to issues. A maintained version that tracks Google's changes, gets fixed the same day something breaks, and works directly on the Antigravity authorization page could capture the people in the issue threads right now. But like the original, it's at Google's mercy.
  3. Just copy the tactic: even if your project isn't about bypassing verification, the move of "find the issue with the most pain, leave a genuinely useful reply with a link" works for anyone, as long as what you've built actually solves the problem in that thread.

How to get users: no ads, no long articles. Leave a reply in the hottest help issue along the lines of "this fixed my problem"; write a step-by-step Chinese guide with screenshots and post it on your blog, linux.do and X; when a platform event happens (this time, the free Ultra 20x), drop a one-line link next to the event thread that same night. Make the README's first screen say clearly what it solves, how to install it, and what to click after installing.

When to move: act as soon as the platform changes its rules. The first week or two, when the first wave of stuck people pours in, is the most valuable window. Once Google closes the gap or ships an official downgrade path, this route is closed.

Signs you misread it: ① Google closes the gap within the next month or two while the repo's stars keep climbing. That would mean people want "someone who provides an exit" rather than "something that works," so the value of a maintained version is bigger than it looks. ② The opposite: after 11-18 the stars fall back to single digits a day and the issue threads are left with only "broken again." That would mean the traffic came from a one-off event and the window for following up has closed. ③ Someone ships an equivalent one-click tool, lists it on a store or adds Firefox support, and passes it within days. That would mean the "fix what it does poorly" route is open, but you need to move fast.

---

Data and sources: the README of GitHub repo havenicec/google-qr-sms-helper, Release download counts, issues, and fork timestamps (11-18); GitHub daily star counts (11-06 to 11-18); lbjlaq/Antigravity-Manager issue #3160 and its comments; nodeseek post-1061490 (Seven's post and replies), post-1061466 / 1061231 / 1061475 and linux.do 3193527 (posts about farming the Ultra 20x promo, 11-17); yyzmiao.top's login troubleshooting guide; X user @Xtsyvq 11-14's long thread; the GitHub pages for zicuharabim/QR-SMS and ShadowHackrs/gmail-account-creator. Whether the tutorial author and the project author are the same person is unverified; the timing of "Google closing the gap" is an inference.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
Manual hacks (scanning with a real Google App / YouTube, spoofing native GMS, Pixel direct pass, PC incognito)OtherFrom ¥2025Issue #3160 and the mainstream answer on linux.do: the most users and the lowest barrierIt turns "luck, environment-dependent, unreliable" into one click in an extension: automated and repeatable
zicuharabim/QR-SMS bookmarklet toolOpen source2026-02About ~3 GitHub stars, GitHub Pages siteBuilt as a bookmarklet with no automatic device environment spoofing, so more primitive and less stable. This one is a one-click extension and fully automatic
Huaduo "auto verification" proxy bypass (guide.rtxk.us / air-rem/antigravity-guide)Other2026-07Paid reseller servicePaid, and you have to hand over your account. This one is free and self-serve, run locally
Bulk Gmail registration bots (ShadowHackrs/gmail-account-creator ~5.9k, Auto-Gmail-Creator and others)Open source2023-2026Thousands of starsBuilt for account sellers mass-producing accounts. The use case is "create a new account," not "get the account I already have logged in," so the target users differ
Official GoogleBig-company features—GlobalOfficially, the only option is "scan again on a real device"; there's no official fallback to SMS. That's exactly the room this tool occupies
Where users come from
  • Verified Traffic: replies on a popular issue in a large repo: lbjlaq/Antigravity-Manager (33,249 stars) issue #3160 (43 comments, unresolved for six months), where li-ming1 recommended it on 10-30 and got +3 reactions; 11-01 another workaround roundup also lists it
  • Verified Content: reposts of Chinese technical tutorials: yyzmiao.top's troubleshooting guide has a full section teaching this tool (text matches the README); X @Xtsyvq 11-14 long thread, Step 2; a Russian-language VK/TG channel repost
  • Verified Platform event: 0 wave of farming Ultra 20x + nodeseek traffic: 11-17 nodeseek/linux.do posts offering "free Ultra 20x" (post-1061231/1061466/1061475), burner accounts flagged by risk controls when logging into Antigravity needed verification; at the same time Seven posted post-1061490 promoting this extension, and forks spiked 5 at 15:47-15:51 UTC, with +75 stars that day
  • Verified Store search / SEO: not listed on the Chrome Web Store, so users have to download the zip and load it manually; aggregator sites like repositorystats and gh-trending index it automatically

havenicec/google-qr-sms-helper: why it works

Data as of 2026-11-18 (GitHub API readings that day + our daily snapshots of the github library).

Bottom line

A Chrome extension with just 4 files that fixes a login roadblock Google built itself 2026 years ago. Chinese users signing in to Google Antigravity / Cloud Shell get asked to scan a QR code, then send an overseas SMS from their phone. China's carriers can't deliver that text, so people loop forever. The extension switches verification back to a phone number and a 6-digit code. It has no paid acquisition and no store distribution. The stars came entirely from people already stuck and hunting for a fix: first a post in the reply thread of a hot help issue on the 33k-star Antigravity-Manager repo, then Chinese tutorials that reposted it, and finally a nodeseek thread during the 11-17 evening "0 yuan for free Ultra 20x" account-farming wave (alt accounts got flagged and needed verification) that sent 75 stars in a single day.

What it is

  • Repo: github.com/havenicec/google-qr-sms-helper, created 2026-10-26, MIT license, JavaScript, one Release (v1.1.0). Last commit 10-28, 4 commits in total. Commits are signed Deng, GitHub account havenicec (registered 2022, 7 followers; this is his only repo with stars).
  • What it does: a Manifest V3 browser extension that switches Google's desktop "cross-device QR scan + outbound SMS" verification flow back to the traditional "enter your phone number and receive a 6-digit SMS code" flow. Targets Chrome, Edge and Brave. Most of the README is a Chinese step-by-step guide with screenshots plus an FAQ.
  • Distribution: Not on the Chrome Web Store (these tool stores won't accept it). You download the zip and load it via developer mode "Load unpacked", or git clone. The bar is a bit high, but the target users (developers, people chasing free AI quota) don't mind.

Data (adoption curve)

DatestarforkSource
11-062110github repo_day
11-103715Same as above
11-145719Same as above
11-166919Same as above
11-178922Same as above
11-1816435Same as above (+75 in a single day)
11-18 later17438Live GitHub API
  • The Release google-qr-sms-helper-v1.1.0.zip was downloaded 915 times (GitHub API, 11-18), more than 5 times the star count; fork/star ratio about 22%. That suggests people really downloaded it to use, not just watched.
  • In the fork list of 11-18, 11-17 15:47–15:51 UTC shows 5 forks in a row within 4 minutes (xtt1997, PillerC, LyncolnWhiteapq9718, bywenshu, Nzy-k), matching the publish time of the nodeseek post below. The adoption spike was driven directly by that post.
  • All 5 issues are Chinese users asking "the verification box doesn't pop up", "it still bounces back to the QR code", "did my account get banned?", and one says "it works, awesome". The author replied to none of them and seems to have stopped maintaining it after release.
  • Not on GitHub trending (the repo is under 60 days old; in our database trending only includes repos at least 60 days old, so this says nothing either way).

1. Why it took off

1. The pain point was created by Google itself

  • Over 2025–2026 years Google changed registration and risk-check verification from "enter a captcha" to "scan a QR code, and your phone sends Google a text message" (Privacy Guides forum 36082, HN item 48094155, r/phishing 1p359w8 all discuss it). Accounts with heavy risk flags are left with only this route.
  • Chinese users are stuck by default: domestic phones lack the full Google Mobile Services framework, and carriers block outbound SMS to overseas short codes. CSDN, Juejin, Zhihu p/2049964878614507830, several linux.do threads (3129211 / 3097512 / 3181126) and nodeseek post-496789 are all requests for help of this kind.
  • Google Antigravity (the agent IDE that's blowing up this year) puts this pain point on full display. Signing in to Antigravity and activating Cloud Shell both trigger account-level verification. The telltale evidence is issue #3160 on lbjlaq/Antigravity-Manager (33,249 stars), "Antigravity pops up phone QR-code verification": opened 2026-05-29, 43 comments, unresolved for half a year. People have tried everything: emulators, various phone brands, scanning with the Google App, YouTube verification, Firefox, none of it reliable. Someone even wrote, "I've never used a reverse proxy or multi-account manager, and I still got flagged just using it normally." Demand density is very high.

2. Users came from a few paths that anyone stuck would find

TimelineChannelEvidence
10-30Antigravity-Manager issue #3160 repliesli-ming1: "...the google-qr-sms-helper project solved it for me" (+3 reactions); 11-01 another five-solutions roundup post also lists it
Blog tagged 10-01 (in reality no earlier than the repo creation date 10-26)Chinese tech blog yyzmiao.topThe section "Google Antigravity login pitfall guide" teaches this extension in full, with text closely matching the README. The blogger's GitHub account yyzmia1 was 10-03 newly registered.
11-14X@Xtsyvq long post "Full walkthrough for fully opening Google Antigravity × Gemini 4 in the China region", Step 2 is this extension. Reach unverified; x-radar corpus 0 posts.
NovemberVK/Telegram Russian AI channel "Зона ИИ"wall-234167215_1804 repost introduction
11-17 around 15:50 UTCnodeseekSeven posted "Seeing everyone farm 20x, here's a pretty handy tool to get around the anti-gravity device and send the SMS". The body was just one line with a link, and the replies below were flooded with "good stuff, starred".
OngoingAggregator sitesAuto-indexed by repositorystats.com and gh-trending.bintini.com

11-06→11-16 gained +2~8 stars a day, a long tail from issue replies and tutorials. The real burst was 11-17/18.

3. 11-17 platform event: the "0 yuan Ultra 20x" freebie wave

  • 11-17 nodeseek and linux.do simultaneously saw a flood of posts teaching people to claim one month or even a year of Gemini Ultra 20x for free with alt accounts (nodeseek post-1061231 / 1061466 / 1061475, linux.do 3193527 and others). OPs all stressed "don't use your main account, use an alt".
  • After claiming on an alt and logging into Antigravity, accounts were immediately risk-flagged and asked for SMS verification (post-1061466 page 2: "just farmed a month and the account got risk-flagged, needs SMS verification", "I see lots of people now have to verify"). Seven's post delivered this extension straight to the people who needed it most. Hence the fork burst on 15:47–15:51 and +75 stars that day.
  • The underlying demand was long-standing: nodeseek always had carpool, resale and find-a-ride posts for "Ultra 20x Antigravity exclusive 300–500 yuan/month", and plenty of US Google alts needed verification.

2. Differentiation: how others handle the same problem

There are three tiers for "turning Google's QR verification back into SMS". This extension sits on the easiest one:

  • Manual hacks (most common, lowest barrier): scan the QR in the Google app or YouTube on a real phone, use a phone that runs the native Google framework, Pixel passes directly, or try the PC incognito mode and hope. The mainstream answers in issue #3160 and linux.do are these. Success depends on the environment and is unstable, and none of it scales. This extension's edge is turning "hope" into "one click".
  • Bookmarklet tool zicuharabim/QR-SMS (GitHub Pages, about 3 stars, created 2026-02): also extracts the verification URL from the QR page and tries clicking "Send SMS", but as a bookmarklet with no automatic UA spoofing. Rawer and less stable.
  • Paid verification service: guide.rtxk.us "Huadu auto-verify", behind air-rem/antigravity-guide. Order and it's delivered instantly, a human verifies for you. A substitute for people who don't want to fiddle, but you pay and hand over the account.
  • Bulk Gmail account creators (ShadowHackrs/gmail-account-creator ~5.9k stars, ai-to-ai/Auto-Gmail-Creator, jocasta-debug/gmail-account-automation): another scenario aimed at account farms mass-producing accounts. Not the personal "I need to log into this one account" case, so different target users.
  • Big-company feature: Google officially only offers "scan the QR on another real phone", with no official downgrade path. That gap is exactly where this tool lives.

What makes it different: among similar tools, it's the only one that chains the full pipeline (recognize the QR → call internal state → spoof the device environment → jump to the SMS option) into one click, fully automatic, with no manual browser device-emulation changes, and it's tied to the hottest scenario right now, Antigravity. That "saves effort + rides the Antigravity hype" combo is why it spread faster than the QR-SMS bookmarklet or manual tutorials.

3. How many people know about it

It's circulating in niche circles, hasn't broken out yet. Evidence:

  • Revenue: not applicable (open source, no revenue), no TrustMRR or revenue posts.
  • Media/big accounts: no tech media or big X accounts covered it; x-radar corpus has 0 posts. Spread concentrated in nodeseek, linux.do, yyzmiao.top type Chinese tech communities and one Russian AI channel.
  • Buzz: +75 in a single day is strong, but the base is small (160+ stars total) and it relies heavily on a one-off freebie event, not steady growth.
  • Copycats: no obvious feature-copy repos. zicuharabim/QR-SMS came earlier (2026-02), so it's an independent solution, not a copy. Among the 35 forks I found no renamed and republished competitors; most look like personal backups.

4. What to borrow

  1. Find a fresh pain point a big company just created and that's still bleeding: Google changed its verification flow 2026 years ago and Antigravity went viral, and together they created a new and dense must-have. "Pits the platform dug itself" is fertile ground for open-source projects to take off.
  2. Put your solution in the most painful issue: no ads, just drop one real, useful link in the 33k-star project's issue that's been unresolved for half a year and gets replies every day. More precise than any paid promotion.
  3. One-click + step-by-step Chinese tutorial: the same principle was built by others as a bookmarklet or manual steps. This one ships as one click plus an illustrated FAQ, directly capturing people who find the manual route too annoying.
  4. Ride a platform event's time window: hand over the solution while the Ultra 20x freebie wave is at its peak. The traffic is ready-made.

V. What's still unclear

  • Whether Seven (nodeseek), yyzmiao, @Xtsyvq and the author havenicec are the same person or coordinated is unverified. Several tutorials match the README almost word for word, so self-promotion is possible.
  • It relies on Google's undocumented internal interfaces and device-verification rules, which Google could patch at any time. Since 11-16 there have already been issues reporting "it stopped working / bounces back to QR" (#3 #4), so real usability is doubtful, and the heat may come fast and go fast.
  • The zip's 915 downloads can't distinguish real use from browsing downloads. Real retention is unknown.

---

Sources

  • Repo / Release / commit / issue / fork timestamps: GitHub API, 2026-11-18.
  • Daily star/fork: our github repo_day (from 2026-10-28).
  • Traffic-driving issue: github.com/lbjlaq/Antigravity-Manager/issues/3160 (43 comments, li-ming1 10-30 reply).
  • Tutorials: yyzmiao.top/2026/10/01/google-antigravity-login-guide/; air-rem/antigravity-guide and guide.rtxk.us; x.com/Xtsyvq/status/2121516168057966754.
  • Freebie wave: nodeseek post-1061231 / 1061466 / 1061475 / 1061490, linux.do/t/topic/3193527.
  • Competitors: zicuharabim/QR-SMS; a Chrome Store search (chromestore) found no similar extension; batch registrars such as ShadowHackrs/gmail-account-creator.
  • Pain background: Privacy Guides 36082, HN 48094155, linux.do 3129211/3097512/3181126 and others.

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