npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sanketsudake/chrome-cdp

v0.3.2

Published

Drive your already-running local Chrome from the command line over CDP. This package is a shim that downloads the matching prebuilt chrome-cdp binary.

Readme

@sanketsudake/chrome-cdp

This package is a thin shim, not the CLI itself. On install it downloads the matching prebuilt chrome-cdp binary from the GitHub release for your platform and verifies its checksum.

npm i -g @sanketsudake/chrome-cdp
# or:
npx @sanketsudake/chrome-cdp doctor

Supported platforms: macOS (arm64, amd64), Linux (amd64, arm64), Windows (amd64, arm64). Extraction shells out to the system tar binary, which ships with macOS, Linux, and Windows 10+.

If the download fails, install another way instead:

brew install sanketsudake/tap/chrome-cdp
# or:
go install github.com/sanketsudake/chrome-cdp-cli/cmd/chrome-cdp@latest

See the main README for full usage.

Trust model

The installer downloads the release archive and checksums.txt from the same GitHub release, over the same HTTPS connection, and verifies the archive's SHA-256 against the entry in checksums.txt before it extracts anything. This check confirms integrity: the bytes you got are the bytes that release published, and the download was not corrupted or altered in transit. It does not add authenticity beyond what GitHub's own account and release security already provide, because checksums.txt comes from that same release and is not signed or verified against an independent, out-of-band source. If you need a stronger guarantee than "GitHub's release for this repo was not tampered with," build from source or verify a signed artifact instead.