GoogleChromeLabs/lighthousebot
Run Lighthouse in CI, as a web service, using Docker. Pass/Fail GH pull requests. observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3458
- days_rel: n/a
- days_push: 2248
- n_releases_24m: 0
Adoption not part of the score
2221 stars · 125 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A deprecated web service and Docker-based tool for running Google Lighthouse audits in CI, reporting pass/fail scores on GitHub pull requests. It has been superseded by the official Lighthouse CI project.
Use cases
- run lighthouse audits in ci
- test pwa scores on github pull requests
- fail ci builds when lighthouse score regresses
- run lighthouse in docker container
- integrate lighthouse with travis ci
When to choose
- you maintain a legacy Travis-based pipeline that already uses it
- you need a historical reference for how Lighthouse CI automation evolved
When to avoid
- starting a new project - use Lighthouse CI instead
- you need CI support beyond Travis
- you require uptime guarantees or maintained infrastructure
Facets
service · maturity abandoned
testing ci-cd monitoring web-development developer-tools testing performance lighthouse pwa-auditing github-pull-requests travis-ci headless-chrome deprecated docker web-server nodejs
1 source
- readme: https://github.com/GoogleChromeLabs/lighthousebot · fetched 2026-08-28 · 67e4d8ca6fdb
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| GoogleChromeLabs/lighthousebot | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="GoogleChromeLabs/lighthousebot")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem