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

nomsentry

v1.1.1

Published

Deterministic identifier policy and deception detection engine

Readme

Nomsentry

Deterministic identifier policy and deception detection engine.

Nomsentry evaluates identifiers like usernames, tenant slugs, and tenant names against a compiled ruleset and returns:

  • allow
  • review
  • reject

It is designed for signup, workspace creation, and naming workflows where impersonation, reserved technical names, profanity, and brand-risk signals should be handled consistently.

Install

npm install nomsentry

Requires Node.js >=20.

CLI quick start

npx nomsentry check support
npx nomsentry explain "example value"

Typical output:

  • check prints one of allow, review, reject
  • explain prints JSON with matched rules and reasons

Optional explicit kind:

npx nomsentry check support --kind default

Library quick start

import {
  createEngine,
  loadRuntimeBundle,
  defaultKind,
  defaultPolicy,
} from "nomsentry";

const bundle = loadRuntimeBundle();
const engine = createEngine({
  sources: [bundle],
  policies: [defaultPolicy],
});

const result = engine.evaluate({ value: "support" });
console.log(result.decision);

defaultPolicy is one strict baseline policy for the single defaultKind. Meaning:

  • technical/reserved, impersonation, profanity-like, and composite risk hits -> reject
  • protected brand hits -> review
  • mixed-script/script risk -> review

defaultKind is exported for explicit calls when needed:

engine.evaluate({ kind: defaultKind, value: "support" });

Use check for a final decision and explain when you need matched reasons for logs or moderation tooling.

Runtime artifacts

  • dist/runtime-sources.json.br: compiled runtime bundle (default)
  • dist/build-manifest.json: machine-readable provenance manifest

Full documentation

The npm README is intentionally short. Full project documentation is maintained in GitHub:

  • Repository: https://github.com/svenschaefer/nomsentry
  • Docs index: https://github.com/svenschaefer/nomsentry/tree/main/docs
  • Third-party notices: https://github.com/svenschaefer/nomsentry/blob/main/THIRD_PARTY_NOTICES.md
  • Security policy: https://github.com/svenschaefer/nomsentry/blob/main/SECURITY.md