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

@ferrow/http-status-catalog

v1.0.0

Published

Complete HTTP status code reference with IANA registry data, lookup utilities, and category helpers

Readme

http-status-catalog

CI

Complete HTTP status code reference with IANA registry data, lookup utilities, and category helpers.

Quick Start

import { lookup, isRetryable } from "http-status-catalog";

const status = lookup(429);
console.log(`${status.code} ${status.name}`); // 429 Too Many Requests
console.log(`Retryable: ${status.retryable}`); // true

API

lookup(code: number): StatusInfo | undefined

Get detailed information for a specific HTTP status code.

interface StatusInfo {
  code: number;
  name: string;
  category: string;
  description: string;
  retryable: boolean;
  cacheable: boolean;
  rfc?: string;
}

isClientError(code: number): boolean

Check if code is 4xx.

isServerError(code: number): boolean

Check if code is 5xx.

isRetryable(code: number): boolean

Check if the status code suggests a retryable error (408, 429, 500, 502, 503, 504, 507, 421, 425).

isCacheable(code: number): boolean

Check if the status code is cacheable by default.

getByCategory(category: string): StatusInfo[]

Get all codes in a category: informational, success, redirection, client-error, server-error.

getCategories(): string[]

Get all available category names.

getAll(): StatusInfo[]

Get all status codes, sorted by code.

Limits

  • Static registry; no updates without new release
  • Covers all IANA-assigned codes through RFC 8470
  • No vendor-specific or non-standard codes

Part of the ferrow-toolkit collection · Sponsored by Ferrow