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

@floodlight/crawler

v0.0.10

Published

floodlight enterprise crawler with continuation

Readme

Crawler for web accessibility

This is a web accessibility crawler written in Node.js

Getting Started

To get started with the crawler, follow these steps:

  1. Install dependencies with npm install
  2. Run the crawler for a domain with DOMAIN=<domain> npm run crawl. For example, DOMAIN=deranged.dk npm run crawl runs for deranged.dk and www.deranged.dk. DOMAIN defaults to digst.dk.
  • You can also set a env var LIMIT to limit the number of pages crawled in the crawl. E.g. DOMAIN=kbhbilleder.dk LIMIT=10000 npm run crawl to limit to ten thousand pages that finish evaluation (skipped or failed pages do not count towards the total).

Running on Ubuntu

When running the crawler locally on ubuntu, you can get an error because of AppArmor which restricts puppeteer.

You need to run the following script, where CHROMIUM_BUILD_PATH is the path to puppeteer's chrome. Example: /home/user/.cache/puppeteer/chrome/linux-140.0.7339.80/chrome-linux64/chrome. The correct path can be found in the AppArmor error message.

export CHROMIUM_BUILD_PATH=/@{HOME}/chromium/src/out/**/chrome
cat | sudo tee /etc/apparmor.d/chrome-dev-builds <<EOF
abi <abi/4.0>,
include <tunables/global>

profile chrome $CHROMIUM_BUILD_PATH flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists <local/chrome>
}
EOF
sudo service apparmor reload  # reload AppArmor profiles to include the new one