Honey is about as established as Chrome extensions get: 12 million users, a 4.58 average rating across nearly 180,000 reviews, and backing from PayPal. We ran it through Validors anyway, because listing quality and user trust are two different things - and it's a good example of what shows up even on a mature, well-loved extension.
What scored well
- Manifest V3. Fully migrated, no deprecation risk.
- Visual assets. Five screenshots, a clear icon, a small promo tile in place, and a first screenshot that states the value proposition plainly.
- Social proof. A 4.58 rating average and the Featured badge both came back clean.
What's actually holding it back
Broad host permissions (confirmed_policy, high severity). Honey's manifest requests http://*/* and https://*/* - unrestricted access to every site you visit. Chrome's review process treats this as a red flag requiring escalated scrutiny, regardless of how legitimate the underlying feature is (finding coupons across arbitrary shopping sites is a real reason to need broad access, but "real reason" and "flagged for review" aren't mutually exclusive).
Keyword repetition (confirmed_policy, medium severity). The listing description uses "Honey" more than five times. It's the extension's own name, so the actual risk here is low - but Chrome's automated review doesn't know that context, it just counts.
Listing content is stale (best_practice_unproven, low severity). The store listing's description and screenshots haven't been touched in years, even though the extension itself ships regular code updates. This is exactly the kind of finding Validors labels as unproven on purpose: freshness of the listing text is a plausible signal, not a documented ranking factor, and it can lag well behind an extension's actual maintenance status.
The takeaway
Nothing here threatens Honey's listing - it's a 71.7/100, solidly in "healthy but leaving points on the table" territory. That's the more common outcome than either a perfect score or a policy violation, and it's why Validors separates "Chrome will flag this" from "this might help, unproven" instead of collapsing both into one generic checklist.