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

@stll/anonymize-data

v0.0.5

Published

Deny list dictionaries and config data for @stll/anonymize

Readme

@stll/anonymize-data

Published configuration data and dictionary catalogs for @stll/anonymize.

This package is the stable data surface for the runtime package. It exists so the runtime can stay focused on detection logic while the published deny-list and trigger assets remain versioned separately.

What ships

  • config/ for trigger, stopword, legal form, and coreference configuration
  • dictionaries/names/ for first names, surnames, titles, and global fallback lists
  • dictionaries/cities/ for country-specific city corpora
  • dictionaries/banks/, dictionaries/courts/, dictionaries/insurance/, dictionaries/education/, dictionaries/government/, dictionaries/healthcare/, and dictionaries/international/ for organization and institution deny-lists

Install

bun add @stll/anonymize-data

Usage

import triggers from "@stll/anonymize-data/config/triggers.cs.json";
import cities from "@stll/anonymize-data/dictionaries/cities/CZ.json";
import banks from "@stll/anonymize-data/dictionaries/banks/US.json";

Maintenance

  • The package build checks trigger configs for schema mistakes and duplicate trigger collisions.
  • The npm tarball is expected to contain every exported dictionary path listed in package.json.
  • Release automation should validate the packed file list before anything is published.