/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

GoogleChrome/lighthouse

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T19:53:02.093Z

1mo ago

GoogleChrome/lighthouse

GoogleChrome/lighthouse is a large, active Node.js/TypeScript project for automated web app and web page auditing, focused on performance metrics and best-practice checks. It is widely used, with 29,983 stars and 9,694 forks, and the repo was updated on 2026-03-30. The repository includes a CLI, Chrome DevTools integration, report generation, viewer/treemap tools, and build/test infrastructure.

Loading tags...

Stars29,983

Forks9,694

Default branchmain

Last pushed2026-03-30T19:06:40Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you explicitly want an older, heavily modified Lighthouse snapshot and are prepared to maintain it yourself. If you want current Lighthouse capabilities, this fork is too stale and too divergent to be a low-risk adoption.

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.

Fork comparison

satya-nutella/lighthouse

38/100

stale

significant_divergence

Choose this fork only if you explicitly want an older, heavily modified Lighthouse snapshot and are prepared to maintain it yourself. If you want current Lighthouse capabilities, this fork is too stale and too divergent to be a low-risk adoption.

Likely purpose

Users who wanted an older Lighthouse base to experiment on, especially for custom audits, report UI changes, or internal tooling that did not need to track upstream releases.

Best for

Teams maintaining an old Lighthouse integration.; Developers experimenting with custom audits or report UX on an older codebase.; Users who need a fixed snapshot more than current feature parity.; People who can absorb merge debt and want to own long-term maintenance.

Additional features

Adds a viewport audit as a performance diagnostic.
Adds an LCP lazy-loaded audit.
Adds a navigation sidebar in the report UI.
Adds config validation for FR.
Treats filesystem resources as non-network.
Includes work that affects DevTools bundle behavior and Chromium download handling in tests/builds.

Missing features

Missing years of upstream maintenance and bug fixes after 2021.
Missing the current Node 22.19+ runtime requirement and modern packaging/tooling from upstream.
Missing newer upstream features such as the baseline compatibility audit and WebDX feature-usage trace category.
Missing newer client/build outputs such as the DevTools MCP bundle and current extension/build workflow updates.
Likely lacks many upstream test, trace, and sample-artifact refreshes from 2026.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Can be useful as a frozen baseline for legacy integrations.
Preserves Lighthouse's core auditing/reporting model.
Large historical diff suggests it already contains substantial bespoke behavior.
May be easier to reason about if you need an older, stable code snapshot.

Risks

Very stale relative to upstream, so security, compatibility, and correctness drift are likely.
Large divergence makes future rebases expensive.
Old Node/runtime and build assumptions may break in modern environments.
Upstream bug fixes and new audits will not be present unless manually ported.