Chrome, Firefox, VS Code & JetBrains Plugins Tracker
Pricing
from $1.50 / 1,000 extensions
Chrome Web Store, Firefox, VS Code, Open VSX & JetBrains plugins in one run: users, ratings, reviews + complaint insights, permission risk, publishers, niche reports, alerts. $1.50/1k.
"publishers" groups the matching extensions by publisher and loads each publisher's portfolio on that marketplace (VS Code, Open VSX, Firefox and JetBrains: the full list by publisher; Chrome: found by searching the developer name, matched by developer id): extension count, total installs, total ratings, weighted average rating, top extension, website domain, GitHub repos, last update, stale extensions and the extensions list. In monitor modes alerts on new publishers, new / removed extensions, installs up/down and rating changes. Charged per publisher row; reviews are not collected in this mode.
Which marketplaces to query. Every search term / publisher is run on each selected marketplace. Chrome Web Store supports search terms and extension IDs (no publisher or whole-store browsing). JetBrains Marketplace covers plugins for IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, PhpStorm, CLion, Android Studio and other JetBrains IDEs. Default when left empty: the four browser / VS Code marketplaces.
[ "chrome", "vscode", "openvsx", "firefox"]Keywords to search, e.g. "ai assistant", "tailwind", "password manager". Leave empty to browse the top list (optionally within a category).
Keep only results whose name, ID, description, tags or categories contain every word of the search term. Marketplaces otherwise return loosely related popular extensions when sorting by installs.
List all extensions of these publishers: VS Code publisher ID (e.g. "ms-python"), Open VSX namespace (e.g. "redhat"), Firefox author username/ID (e.g. "bitwarden") or JetBrains Marketplace vendor (e.g. "JetBrains", "Red Hat"). Not available for Chrome Web Store.
Track exact extensions: "chrome:<32-letter ID>", "vscode:ms-python.python", "openvsx:redhat.java", "firefox:ublock-origin", "jetbrains:17718" (or the plugin's XML id, e.g. "jetbrains:com.github.copilot") or full marketplace URLs (Chrome Web Store and plugins.jetbrains.com URLs too). Without prefix, a 32-letter ID is Chrome, a number is JetBrains, "publisher.name" is looked up on VS Code + Open VSX and a plain slug on Firefox.
Optional category filter, e.g. "AI", "Programming Languages", "Themes", "Linters", "Debuggers", "Snippets", "Chat", "Formatters", "Testing", "Data Science".
Optional Firefox category slug, e.g. "privacy-security", "tabs", "search-tools", "download-management", "appearance", "other".
Optional JetBrains Marketplace tag filter, e.g. "AI", "Code Tools", "Theme", "Framework", "Programming Language", "Tools Integration", "Productivity".
Optional: only plugins compatible with this JetBrains IDE, e.g. "idea" (IntelliJ IDEA), "pycharm", "webstorm", "goland", "rider", "phpstorm", "clion", "rubymine", "androidstudio", "dataspell".
Ranking used for search and browse lists. The rank field and rank-change tracking follow this order. Chrome Web Store search is always ordered by the store's own relevance.
Max extensions per search term / publisher / category list per marketplace.
Publishers mode only: load at most this many extensions per publisher (most installed first). portfolioComplete is false when the cap is hit (and always for Chrome, which has no developer listing).
Skip extensions below this many installs (VS Code), downloads (Open VSX, JetBrains), users (Chrome) or daily users (Firefox).
Output only Chrome / Firefox extensions whose permission risk is at least this level (VS Code, Open VSX and JetBrains have no permission model and are excluded when set). Every Chrome and Firefox row gets permissionRiskScore (0–100), permissionRiskLevel, allSitesAccess and riskyPermissions with a plain-English reason (e.g. cookies, webRequest, debugger, access to all websites).
Extensions not updated for more than this many days get isStale = true (abandoned-extension finder).
"new" and "changed" compare with the previous run of the same monitor name. The first run is the baseline and outputs everything.
Save a snapshot and add previousInstalls, installsChange, rankChange, previousVersion and changeTypes even when outputting all results.
An installs-up / installs-down change is reported when installs moved at least this many percent since the last run.
A rank-up / rank-down change is reported when the position moved at least this many places.
Snapshot name used for change tracking. Use a different name for each separate monitor/schedule.
Also output one market-report row per marketplace × search term / publisher / category (recordType = "market-report"): total extensions in the store, installs (total, median, distribution), market concentration (top 1 / 3 / 10 install share), average and rating-weighted rating, rating distribution, pricing mix, update freshness, new extensions in the last 90 / 365 days, permission-risk mix and all-sites access share (Chrome, Firefox), Chrome extensions still on Manifest V2, top publishers, VS Code weekly trending, weak incumbents (big but rated below 3.8), stale incumbents (big but not updated for a year), rising newcomers and plain-English opportunity signals. With trackChanges or a monitor output mode it adds what changed since the last run. Uses the same filters (minInstalls, minPermissionRisk) and maxResultsPerQuery as the extension rows.
Output only the market-report rows (no extension, publisher or review rows). Use this to size a niche before building an extension. Each report is charged as one market-report event; extensions analysed for it are not charged.
Also output one review-insights row per matched extension (recordType = "review-insights") from its newest reviews (up to "Max reviews per extension"): rating distribution, negative / positive share, rating trend (last 90 days vs older), top complaint themes in 1-3 star reviews (bugs, broke after update, browser / IDE compatibility incl. Manifest V3, performance & memory, breaks sites, ads & hijacking, privacy, paywall, login, sync & data loss, accuracy, UI, developer support) with example quotes, top praise themes in 4-5 star reviews, feature requests, common complaint phrases, rating by extension version with problem releases (a version rated 0.7+ stars below the others), monthly trend and developer reply rate / speed. With 2+ extensions of 10+ reviews a review-comparison row benchmarks them (themes per 100 reviews, relative weaknesses and strengths). Works on Chrome, Firefox, VS Code and JetBrains; works without "Include user reviews" (reviews read for insights are not charged).
Also output user reviews for every matched extension as separate rows (recordType = "review"): star rating, review text, date, extension version, helpful votes (Chrome) and the developer's reply. Works on Chrome Web Store, Firefox Add-ons, VS Code Marketplace and JetBrains Marketplace. Reviewer names are not collected. In "new"/"changed" output modes only reviews posted since the previous run are returned.
Upper limit of review rows per extension (after the star and date filters).
Order in which reviews are collected. "helpful" and "lowest" use the Chrome Web Store's own sort; Firefox, VS Code and JetBrains always return newest first.
Keep only reviews with this many stars or fewer, e.g. 2 = complaints only (bug reports, churn reasons, feature requests). 5 = all reviews.