Sector Radar

Chrome Extension Starters

Diversum analyzed 24 fork-and-build Chrome extension starter repositories to map the 2026 default pattern, where builders still have meaningful choices, and which search results are historical rather than current-era starting points.

Strong Default
54%
Category Leader
25%
Baseline Implementation
13%
Adjacent Infrastructure
8%
Inactive Scaffold
0%

Corpus denominator: 24 in-cluster Chrome Extension Starters. Evidence snapshot: 2026-05-12.

Interactive evidence graph

Explore why starter repositories cluster together.

Connections are generated from report evidence: shared centroid traits, build tool, UI framework, extension surface, and manifest generation.

What we found

A modern default has formed very quickly.

This is a radar, not a leaderboard. The report maps sector position and evidence patterns rather than declaring winners.

Sharp convergence

MV3 + TypeScript + Vite + React + HMR is now the fresh-project default, even though older webpack and MV2-era repos still hold substantial star weight.

Low differentiation

54% of the corpus are Strong Defaults: real, useful starters that are hard to distinguish once a builder has chosen the modern stack.

No inactive scaffolds

Every in-cluster repo shows real human engineering. This starter sector filters out empty scaffolds more effectively than younger AI tooling sectors.

Open surface gaps

No in-cluster starter fully owns the MV3 side panel opportunity, full-surface scaffolding, and no-framework TypeScript path at the same time.