Data Methodology

Chrome-Stats tracks public marketplace data for browser extensions and mobile apps. The goal is to make store-level counts, historical trends, ranking signals, and safety-related indicators easier to inspect and cite.

Data sources

Chrome-Stats collects public listing data from Chrome Web Store, Edge Add-on Store, Firefox Add-ons Store, Google Play Store, and Apple App Store. Depending on the marketplace, discovery uses public store pages, public category and collection pages, public search/listing surfaces, and official store sitemap feeds when they are available.

The records we store are derived from information already exposed by the marketplaces, such as names, categories, publisher information, ratings, install or download ranges, update dates, versions, permissions, screenshots, descriptions, and review metadata. Availability differs by store because each marketplace exposes a different set of fields.

Refresh process

Store data is refreshed continuously, with public statistics pages built from the latest stable daily snapshot. Each snapshot is available as a CSV download from the raw data export page. When a listing can no longer be found, Chrome-Stats marks it as removed or obsolete rather than silently deleting its history.

Frequently changing data, such as ratings, reviews, ranks, user counts, download ranges, and update dates, may be refreshed more often than historical fields. Some store-provided values are rounded, delayed, localized, or visible only in selected regions, so Chrome-Stats reports should be treated as third-party marketplace estimates rather than official store totals.

Normalization

Raw marketplace fields are normalized into a common model so that users can compare extensions and apps across stores. For example, Chrome-Stats maps store-specific item types, categories, permissions, monetization models, rating fields, version fields, and date fields into consistent analytics dimensions where possible.

We preserve platform-specific distinctions when a common field would be misleading. Android download data is based on Google Play Store download ranges, browser extension popularity uses the active-user or user-count values exposed by each extension store, and Apple App Store device support is reported separately because App Store listings can target multiple device families.

Risk and safety signals

Chrome-Stats risk indicators are analytical signals, not a malware verdict. They combine public marketplace data with observable technical metadata such as permissions, host permissions, manifest data, update behavior, publisher patterns, user feedback, and historical changes.

These signals help users and organizations prioritize review. They should be interpreted with context: a powerful permission may be legitimate for one product and unnecessary for another, and a low-risk score does not guarantee that software is safe.

Corrections and limitations

Marketplace pages can change format, hide fields, rate-limit requests, remove listings, or display different data by locale. Chrome-Stats monitors these changes, keeps historical records when possible, and updates parsers when store behavior changes.

Some extensions or apps may not be available on Chrome-Stats even if they exist in a store. This can happen when a developer asks us to remove a listing from the website.

If you notice an incorrect listing, stale value, missing app, or methodology issue, contact support@chrome-stats.com. Include the item URL, the field that looks wrong, and the date you observed the issue.