Chrome Web Store Extensions Scraper
Pricing
$2.00 / 1,000 extensions
Scrape Chrome Web Store extensions: users, precise rating, rating count, version, update date, category, size and manifest permissions. Fast HTTP, no browser, no login.
Pricing
$2.00 / 1,000 extensions
Rating
0.0
(0)
Developer
Alexandre Bobichon
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 hours ago
Last modified
Categories
Share
mode: "categories"): scan the public pages of up to 18 store categories, each listing its top 32 extensions, and scrape the matching ones. Filters minUsers, minRating, keyword and maxPermissionRiskLevel are applied to the category listing before any extension page is read, so non-matching extensions cost nothing. maxItems caps the number of extensions across categories.extensions is no longer required (it is used with the default mode: "extensions").SUMMARY.discovery reports requested, scanned and unreadable categories, listed and matching extensions. A run fails only if no category page could be read; no match for the filters is a successful run.trackChanges): each extension is compared with its state from the previous tracked run, kept in a key-value store of the user's account (stateStoreName). New output fields changeStatus (new, changed, unchanged), changedFields, previousValues and previousScrapedAt, all null when tracking is off. Rating moves below 0.01 are ignored without hiding slow drifts.onlyChanges: unchanged extensions are not saved to the dataset, so they are not charged.SUMMARY.changes counts extensions per status, and the final message lists them.allSitesAccess (host permissions or content scripts covering every website), sensitivePermissions (required permissions reaching browsing data, network traffic or browser control) and permissionRiskLevel (low, medium, high). They are shown first in the Permissions view.notFoundIds instead of unreadableIds, so unreadableIds only signals a possible page layout change. On 500 random extensions, all 13 previously unreadable pages were of this kind. Warnings for unreadable pages include the HTTP status and page title.users: small extensions show no user count, so a run on a few new extensions could fail wrongly. It now checks version and updatedAt only, and SUMMARY.missingKeyFields lists these two fields.SUMMARY record (warning in the log).users, version or updatedAt is missing on more than half of the scraped extensions, a sign that the store page layout changed. Items already scraped stay in the dataset.SUMMARY gains missingKeyFields (count of scraped extensions without each key field).First public version.
chromewebstore.google.com and legacy chrome.google.com/webstore domains). URLs from other websites are rejected; invalid entries are skipped with a warning, and the run fails if no valid entry remains.maxItems (default 100, max 5,000) limits the number of extensions.categoryName), version, update date, size as displayed and converted to bytes (sizeBytes, approximate because the store rounds it), languages, Featured badge, EU trader status, website / support / privacy policy URLs, minimum Chrome version, manifest version and permissions (required, optional, host), icon, screenshots and videos.includeDescription, enabled by default).Scraped 42 of 100 extensions…), followed by a final summary message.SUMMARY record in the default key-value store (Run summary in the Output tab) lists requested and scraped counts, not found, unreadable and failed extension IDs, invalid input entries (first 100) and whether the cost limit was reached.stream-json (dependency of @crawlee/core), the source of all 5 moderate npm audit --omit=dev alerts. Forcing the patched 3.6.0 breaks Crawlee at runtime (module layout changed), and the Actor never feeds user-controlled JSON to it. Upgrade when Crawlee ships a fix.