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

@intutic/anomaly-taxonomy

v1.10.1

Published

The Intutic runtime anomaly taxonomy — category enum and severity map. Type-only, zero dependencies.

Readme

@intutic/anomaly-taxonomy

The twelve runtime anomaly categories Intutic classifies against, and the severity each carries. Types and constants only — no detection logic, no thresholds, no probes.

npm install @intutic/anomaly-taxonomy
import {
  AnomalyType,
  ANOMALY_SEVERITY_MAP,
  isAnomalyType,
} from '@intutic/anomaly-taxonomy'

ANOMALY_SEVERITY_MAP[AnomalyType.DATA_EXFILTRATION] // 'CRITICAL'
isAnomalyType(notification.category) // narrow an untrusted string

Why this is a package

The taxonomy is declared in two languages. The Rust proxy raises these categories inline on the request path and cannot call into TypeScript, so it keeps its own copy; the control plane classifies against them asynchronously in TypeScript.

Two hand-maintained lists drift, and drift here is silent — a renamed category simply stops being classified downstream, with no error raised anywhere. This package is the source of truth, and the proxy's test suite parses it and fails the build on any divergence.

What it deliberately does not contain

Detection. Deciding whether a request is anomalous involves thresholds, sequence analysis, baselines and probes; sharing the vocabulary should not require sharing any of that. Keeping them apart is what lets the vocabulary be used by anything that needs to read an Intutic verdict.

Apache-2.0.