GoogleChrome/lighthouse

Prefer this fork only if you need its older, customized test and workflow setup. If you want current Lighthouse capabilities or low-maintenance adoption, upstream is the better choice.

Prefer this fork only if you need its legacy/custom behavior and are prepared to own the maintenance burden. For most adopters, upstream Lighthouse is the safer choice because this fork is materially stale and appears to have removed at least one CLI feature.

Choose this fork only if you specifically need its older frozen state or local workflow/fixture changes. For most adopters, upstream is the better choice because it is far more current and actively maintained.

Prefer upstream unless you specifically need this fork's older benchmarking/debug-trace additions. This fork looks like a long-stale, high-maintenance branch with some useful custom instrumentation but a meaningful risk of missing modern Lighthouse behavior and fixes.

Prefer this fork only if you need an old, stable Lighthouse snapshot and are willing to own the divergence. If you want current performance audits, modern tooling, or low-maintenance adoption, upstream is the better choice.

Prefer this fork only if you specifically need the older Lighthouse 12.x line plus the fork’s custom audits and compatibility fixes. If you want current audits, active maintenance, and upstream parity, the main Lighthouse repo is the better choice.

Choose this fork only if you need its custom audits or MCP-oriented workflow and are willing to maintain a long-lived divergence. If you want current Lighthouse behavior, this fork is too stale and too far from upstream to be a low-risk adoption.

Choose this fork only if you need the old report/extension experiments it contains. For anyone wanting a current web auditing platform, upstream Lighthouse is the safer and far more complete base.

Prefer this fork only if you need its older, customized behavior and do not care about staying current. If you want a maintained Lighthouse baseline or modern features, upstream is the better choice.