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

@glasswatch/collector

v0.1.0

Published

Outside-in client-side scan engine: scripts, third parties, headers, trackers, vulnerable libraries, tech stack, and a risk grade.

Downloads

162

Readme

@glasswatch/collector

Outside-in client-side scan engine. Point it at a URL and get a structured report of what runs on the page and how risky it is — scripts and their origins, third-party network destinations, security headers, cookies and trackers, known-vulnerable libraries, tech stack, and an A–F risk grade.

Part of the Glasswatch project. Apache-2.0.

Requirements

  • Node.js ≥ 20.

  • Chromium for Playwright. The collector drives a headless Chromium browser, which is downloaded separately from the npm package. Run this once after installing (and on CI):

    npx playwright install chromium

    Without it, the first scan fails with a "browser not found" error.

CLI

npx @glasswatch/collector https://example.com

Prints a JSON ScanResult.

Library

import { scan } from "@glasswatch/collector";

const result = await scan("https://example.com", { enforceSsrfGuard: true });
console.log(result.grade.letter, result.trackers);

Security: when scanning untrusted, user-supplied URLs on shared infrastructure, always pass { enforceSsrfGuard: true } to refuse private/loopback/metadata targets.

Detection rules

The seed datasets in data/ (trackers.json, known-vulns.json, fingerprints.json) are intentionally small and community-maintainable. Contributions that expand coverage are welcome.