Data sources
Extension names, developers, categories, user counts, ratings, rating counts, versions, last-updated dates, sizes, store URLs, icon URLs, and short descriptions are collected from public Chrome Web Store listings. Requested browser APIs and host patterns come from the extension package manifest. Requested, optional, host, optional host, and content-script match lists are shown separately.
Developer descriptions appear verbatim under “From the developer's store listing”. ExtRadar does not write extension summaries, infer functionality, or generate recommendations.
Export generated: Oct 16, 2026 (UTC).
Missing fields are labeled “Not available.” Missing permission lists are different from collected empty lists. Store user counts may be rounded and can change between collections. Combined user counts are sums across listings, not unique people.
All pages are generated from the backend’s shared JSON export. The website does not request store data or connect to a live database as you browse. Letter tiles are generated from listing names and do not represent original store icons; the original icon URL is linked when available.
Manifest permissions and scope
Detail pages show manifest_version and the exact values collected for permissions, optional_permissions, host_permissions, optional_host_permissions, and content_script_matches. Each list stays separate, preserving its order and repeated values.
Permission scope, its explanations, all-sites access, and sensitive permissions come directly from the backend export. The website does not calculate scope. The backend applies these rules to the collected manifest:
- Broad: required access to all websites and at least one sensitive required browser API.
- Moderate: required access to all websites or a sensitive required browser API, without both.
- Minimal: neither of those capabilities. Specific-site access and other APIs may still be declared.
- Permissions not verified: the manifest could not be read, or its version and all permission lists are unavailable. This is a separate state with no confirmed scope.
All-sites access includes required wildcard-host patterns in host permissions, Manifest V2 permissions, or content-script matches. Specific sites, subdomain wildcards, and local file patterns do not count as all-sites access. Sensitive required APIs are cookies, webRequest, webRequestBlocking, debugger, history, and nativeMessaging. Optional APIs and optional hosts do not affect the backend scope because users must grant them at runtime.
Backend explanations appear verbatim on detail pages. Available lists remain visible when the manifest is unverified; empty fields do not confirm an absence of access. Missing fields show “Not available.” “None declared in the collected data” appears only for an empty list with a verified scope.
These are manifest declarations, not observations of extension behavior. Chrome may restrict access further. Scope does not assess trustworthiness or safety.
Observed change history
History uses collected snapshots and the recorded change feed. The collector records changes in version, requested APIs, host permissions, permission scope, users, and rating. Recorded changes show their detection time, previous value, and new value. An empty feed means no changes have been recorded yet.
For older exports without a change feed, history compares consecutive snapshots of the same extension. It compares available metrics, permission sets, and the backend’s scope and capability fields; array ordering alone is not a change. Scope is always the value recorded by the backend for each observation. A transition to or from unavailable data is an observation about field availability, not proof of changed extension behavior.
With one snapshot and no recorded changes, the listing says “First observed [date]; no changes recorded yet.” No older events are inferred from the store update date. There is no guarantee that every change between snapshots was captured.
The popular, not updated report
The report includes records with known user counts of at least 10,000 and a known last-updated date strictly before Oct 17, 2025. The cutoff is 12 calendar months before the UTC build date, Oct 17, 2026, clamped to the last valid day of the target month. Results are ordered by users, highest first.
Missing user counts or update dates are excluded. The threshold is configurable at build time. A store update date is not evidence of active maintenance, abandonment, vulnerability, or safety.
Independent and untracked
ExtRadar is an independent directory and is not affiliated with Google or the Chrome Web Store. There are no analytics, tracking scripts, payment collection, or paid placements. The submission form is disabled while submissions are closed.