Trending Categories Repositories Insights Dependencies Withheld

Trending Categories Repositories Insights Dependencies Withheld

Trending repositories

Ranked by Attention Score: stars gained over the last 7 complete days

Period

Sort order

Topics: chrome-devtools

Topics

Search topics

No listed topic matches. Press Enter to filter by “”.

Category

Filters

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

5 repositories by Attention Score · Oct 27, 2026 – Nov 2, 2026 (UTC)

Topic: chrome-devtools

1.ChromeDevTools / chrome-devtools-mcp

Chrome DevTools for coding agents

mcp-server
puppeteer
chrome-devtools
browser
chrome
debugging
+2 more

TypeScript APACHE-2.055K total5.2K forks

+484 stars

from 54,140 · score 6.18

2.GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.

audit
best-practices
performance-metrics
pwa
web
performance-analysis
+2 more

JavaScript APACHE-2.031K total9.8K forks

+52 stars

from 30,943 · score 3.97

3.chromedp / chromedp

A faster, simpler way to drive browsers supporting the Chrome DevTools Protocol.

golang
chrome
chrome-debugging-protocol
testing
unit-testing
chrome-devtools
+1 more

Go MIT13K total891 forks

+6 stars

from 13,340 · score 1.95

4.go-rod / rod

A Chrome DevTools Protocol driver for web automation and scraping.

cdp
chrome-headless
chrome-devtools
chrome-devtools-protocol
headless
web-scraping
+11 more

Go MIT7.1K total489 forks

+6 stars

from 7,137 · score 1.95

5.bitcrowd / chromic_pdf

Convenient HTML to PDF/A rendering library for Elixir based on Chrome & Ghostscript

pdf-generation
pdf-converter
pdf
invoice
chrome-devtools
chrome-headless

Elixir APACHE-2.0485 total43 forks

+1 stars

from 484 · score 0.69

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before a repository's first Observation. A longer window needs more days of Observations first. A repository younger than the window is not ranked in it.

The filters narrow the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Category holds the repositories that its published rules match; see Categories.

Repositories enter the index from the Seed Dataset or by gaining stars faster than the published admission threshold, whatever their size. Admission is permanent, so an archived repository can still rank.

Browse the Repository Index

Trending Categories Repositories Insights Dependencies Withheld Withholding Rule Privacy Send feedback