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

@oss-error-registry/core

v0.1.0

Published

Detector contracts and deterministic bounded matching for OSS Error Registry.

Readme

@oss-error-registry/core

Detector contracts, runtime validation, and the bounded deterministic matching engine for OSS Error Registry.

Version 0.1.0 is prepared but has not yet been published to npm. Requires Node.js 22.13.0 or newer and uses ESM.

Install

After publication:

npm install @oss-error-registry/core

For repository development, use the root pnpm workspace instead of installing this package separately.

Usage

import {
  analyze,
  defineDetector,
  type AnalysisResult,
} from "@oss-error-registry/core";

const detector = defineDetector({
  schemaVersion: 1,
  id: "node/module-not-found",
  ecosystem: "node",
  title: "CommonJS module cannot be resolved",
  explanation: "Node.js could not resolve a module requested by CommonJS.",
  match: {
    threshold: 100,
    evidence: [
      {
        id: "cannot-find-module",
        description: "Node.js emitted its Cannot find module error.",
        weight: 100,
        required: true,
        pattern: {
          kind: "substring",
          value: "Error: Cannot find module '",
          caseSensitive: true,
        },
      },
    ],
    exclusions: [],
  },
  likelyCauses: ["The requested package is not installed or resolvable."],
  diagnosticSteps: [{ description: "Inspect the requested module name." }],
  remediation: [
    {
      description: "Verify the package name before changing dependencies.",
      safety: "safe",
    },
  ],
  documentation: [
    {
      title: "Node.js CommonJS module loading",
      url: "https://nodejs.org/api/modules.html#loading-from-node_modules-folders",
    },
  ],
});

const result: AnalysisResult = analyze(
  "Error: Cannot find module 'example-package'",
  [detector],
);

The package root exports analyze(), detector/plugin definition helpers, analysis limits and errors, and their TypeScript types. Internal modules are not exported as package subpaths.

Core accepts text and detector data only. It does not read files, load a registry, format output, execute commands, access a network, or send telemetry.

See the repository README, detector contract, and matching semantics.