\n
\n I’ve shipped 4 Chrome extensions and 2 VS Code extensions. The advice that always sounds smart \u2014 “find a popular extension the dev abandoned, rebuild it better” \u2014 is miserable in practice. You open the Web Store, see 100k users and a 4.4 rating, think you found gold, then burn a weekend reading reviews only to realize half the complaints are unfixable traps (sync died, login broke, backend gone).<\/p>\n
So I built a small pipeline to do the boring part automatically.<\/p>\n
The method<\/p>\n
Scrape public Chrome Web Store metadata \u2014 users, rating, last-updated date.
\nFilter: 20k\u2013300k users, 18+ months without an update, rating 3.3\u20134.4 (good enough to prove demand, bad enough to prove pain).
\nPull up to 50 recent reviews per candidate via public CWS data.
\nScore each one:
\nscore = log10(users)10 + months_stale0.5 + feature_request_count2 – trap_count1.5
\nThe key part is trap_count \u2014 I subtract points for complaints about sync\/login\/server issues, because those are unfixable without inheriting someone else’s dead backend. High “demand” with high trap count is a mirage.<\/p>\n
One example<\/p>\n
Extension Manager \u2014 100k users, 4.4\u2605, last updated ~25 months ago. Looks healthy until you read the 1\u20132\u2605 reviews:<\/p>\n
“The site-specific rules feature simply does not work\u2026 the core feature advertised is broken.”
\n“It won’t save any changes made\u2026 extensions are re-enabled automatically.”
\nA user even posted an RCE report: the dev parses JSON with a Function(str)() fallback \u2014 executing arbitrary code from untrusted input.<\/p>\n
That’s not “build a clone.” That’s “fix the rules engine, kill the eval, add local backup, ship something 100k people already want.”<\/p>\n
The counterintuitive part<\/p>\n
The highest-scoring extension in my list (200k users, abandoned ~4 years) is actually the worst business opportunity \u2014 it’s a simple toggle utility whose users will never pay, and the original asks for camera\/mic permissions (adware-grade). Raw download counts would put it at the top of your build list. Revenue potential buries it.<\/p>\n
That gap between “looks like an opportunity” and “is actually monetizable” is the whole reason I started scoring monetization separately.<\/p>\n
What I did with it<\/p>\n
I analyzed 30 of these \u2014 14 deep-dives and 16 honest “avoid this” verdicts \u2014 with demand, the gap, build difficulty, monetization reality, and why nobody rebuilt it yet. Packaged it with the raw CSV here if it’s useful to anyone: https:\/\/tuanspark85.gumroad.com\/l\/wnnxyq (there’s a free Top-3 preview too).<\/p>\n
Happy to answer questions about the scraping pipeline in the comments \u2014 what tripped me up was the CWS review endpoint and pagination.<\/p>\n