Composer
jQuery
React Native
Babel
OpenSSL
Raven.js
Symfony
jQuery UI
Exstats
ChromeStats
ExtPose
Extension Ranker
CRX4Chrome
CRX Extractor
AppBrain
Chrome Winner
Most browser extension developers ship the same product to Chrome, Edge, and Firefox, then try to track its performance across three separate developer dashboards, three different review feeds, and three sets of keyword rankings. The data is fragmented, history is short, and there is no easy way to compare a release against a competitor over time.
Exstats fixes this by grouping the Chrome, Edge, and Firefox versions of an extension into one product view, alongside the competitors you want to watch. It tracks daily changes in installs, ratings, reviews, category rank, and search rank, then keeps up to a full year of history so weekly and monthly trends are visible at a glance. Email and Slack alerts fire on rating drops, rank shifts, and competitor updates so a regression does not sit unnoticed for a week.
Beyond your own products, the Extension Explorer indexes 280,000+ extensions with 30+ searchable fields and exportable CSV or XLSX, the Keyword Tracker suggests AI-generated keyword ideas and tracks rank by store, and the Store Trends dashboard reports category growth, rating distributions, and review activity across each store.
Composer ExstatsNo Exstats videos yet. You could help us improve this page by suggesting one.
Exstats's answer:
Exstats treats an extension as one product across stores, not as three separate listings on three sites. The Chrome, Edge, and Firefox versions sit in one row, and history, reviews, alerts, and competitor data flow from there.
Exstats's answer:
Exstats started because developers shipping browser extensions kept running into the same wall. The Chrome Web Store, Edge Add-ons, and Firefox Add-ons each give publishers a siloed view with short history, no competitor data, and no way to compare a release against a rival over time. Teams that maintained extensions on more than one store ended up checking three dashboards a day and keeping competitor numbers in spreadsheets. We built Exstats so an extension and its store versions live in one place, with daily history, alerts, and competitor tracking built in.
Exstats's answer:
Unified multi-browser view. Exstats is the only dashboard that groups the Chrome, Edge, and Firefox versions of an extension into one product, with shared history and shared alerts. Most analytics tools cover only the Chrome Web Store, or split the three stores across separate sites.
Full year of daily history. Stores show current numbers and a short trail. Exstats keeps daily snapshots for up to a year so weekly and monthly trends, rating regressions, and competitor launches are visible at a glance.
Reviews from every store in one table. Chrome, Edge, and Firefox reviews sit in one sortable, filterable table, so a developer can read a week of feedback without rotating between three dashboards.
Keyword tracking with AI suggestions. Search rank is tracked per store with daily change indicators, and the keyword tool suggests new keywords from competitor listings rather than expecting the developer to bring a complete list.
Exstats's answer:
Exstats is built for the people shipping and growing browser extensions.
The core audience is independent extension developers and small product teams who need one place to watch installs, ratings, reviews, and keyword rank for their extensions, on whichever stores they publish to.
A second audience is extension growth and marketing specialists who track competitor launches, rating shifts, and category trends on behalf of clients and need a single view across Chrome, Edge, and Firefox rather than three separate workflows.
A third audience is product and engineering teams at companies whose extension is a meaningful acquisition or retention surface, who need daily alerts, exportable data, and API access for internal dashboards.
Based on our record, Composer seems to be more popular. It has been mentiond 152 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
It's very confusing that they use the same name as the very well known PHP package manager, composer https://getcomposer.org/. - Source: Hacker News / 3 months ago
I'm embarrassed I never took the time to understand Composer until now. I have been preaching for a long time to start each PHP project with Composer, even when the project is not going end up on Packagist. - Source: dev.to / 3 months ago
Waaseyaa is a monorepo. The root composer.json defines 43 subpackages under packages/, each referenced as a path repository with @dev constraints. During development, this is convenient. Composer resolves everything locally, and you never think about versioning. - Source: dev.to / 4 months ago
(P)NPM is an outlier in this behavior compared to package managers of other languages. With package managers like Composer (PHP), pip (Python) and NuGet (.NET) dependencies are by default peer dependencies. That means that in those package managers it is not possible to have multiple versions of the same dependency in your application1. - Source: dev.to / 8 months ago
Download from getcomposer.org and follow installation instructions. - Source: dev.to / 10 months ago
jQuery - The Write Less, Do More, JavaScript Library.
ChromeStats - Compare and analyze Chrome extensions and Android Apps
React Native - A framework for building native apps with React
ExtPose - Optimize your Chrome extension to get more installs
Babel - Babel is a compiler for writing next generation JavaScript.
Extension Ranker - Boost your Chrome Extension ranking with the help of Extension Ranker โ driving more impressions, installs, and sustainable user growth.