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

wwwgrep

v0.1.0

Published

🔎 wwwgrep – A Command-Line Tool for Web Scraping & Searching

Downloads

203

Readme

wwwgrep

Sometimes you need to verify that a specific phrase no longer appears on a website. For example, the Legal team may ask you to confirm that a trademarked term, outdated disclaimer, or compliance-related statement has been removed from all public pages.

Searching the underlying content sources is often difficult or impossible. Instead, wwwgrep searches the published website itself. It crawls all publicly accessible pages (ignoring robots.txt) and looks for the specified keywords or substrings.

Use it to verify content removals, compliance updates, rebranding efforts, or any large-scale text changes directly on the live website.

Demo

Install

npm install -g wwwgrep

If installing under sudo, fix permissions first:

sudo chown -R $(whoami) $(npm config get prefix)/{lib/node_modules,bin,share}

Usage

wwwgrep <url> <keyword> [options]

| Argument / Option | Description | |---|---| | <url> | Base URL to start crawling from (e.g. https://example.com) | | <keyword> | Text or regex pattern to search for | | -i | Case-insensitive match | | --regex | Treat keyword as a regular expression | | --depth N | Limit crawl depth (default: unlimited) | | --concurrency N | Number of pages to crawl in parallel (default: 1) | | --max N | Stop after N pages | | --timeout N | Page load timeout in seconds (default: 15) | | --wait N | Extra milliseconds to wait after page load for JS rendering (default: 0) | | --output file | Write matched URLs to a file | | --dump-body | Print the body text of the first page and stop (useful for debugging) | | --help, -h | Show help |

Examples

Search for a keyword across a site:

wwwgrep https://dsheiko.com "Puppetry 3"

Case-insensitive search, limited to 2 levels deep:

wwwgrep https://dsheiko.com puppetry -i --depth 2

Find pages containing an email address (regex):

wwwgrep https://example.com "\w+@\w+\.\w+" --regex

Sample the first 20 pages, save matches to a file:

wwwgrep https://example.com "login" --max 20 --output results.txt

Faster crawl with parallel pages, piped output for scripting:

wwwgrep https://example.com "TODO" --concurrency 4 | grep https

Notes

WSL2 / Docker: the tool runs headless Chromium with --no-sandbox automatically, which is required in containerized environments.

JavaScript-rendered pages: because it uses a real browser, content injected by JavaScript is visible to the search — unlike curl-based tools.

Piped output: when stdout is not a terminal, the progress bar is suppressed and only matched URLs are printed, making it easy to pipe results into other tools.