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/business-registries

v0.3.1

Published

Typed clients for national business / commercial registries (Czech ARES, Norwegian Brreg, Mexican INEGI DENUE, US SEC EDGAR, Slovak ORSR, Taiwanese GCIS, Finnish PRH, Polish KRS, UK Companies House, French INSEE Sirene, ...)

Readme

@stll/business-registries

Typed clients for national business and commercial registries.

Find companies, normalize registry identifiers, and reuse public business data without writing a different scraper for every jurisdiction.

Each jurisdiction lives in its own subpath so consumers import only what they need:

import { lookupByIco } from "@stll/business-registries/ares";

const company = await lookupByIco("27082440");

A namespace re-export is also available from the root entry:

import { ares } from "@stll/business-registries";

await ares.lookupByIco("27082440");

Browser applications initialize the validation runtime once during startup. Calls are safe to share when several features initialize concurrently:

import { initialize } from "@stll/business-registries/browser";

await initialize();

Registry identifier validators stay synchronous after initialization. Calling one before the runtime is ready throws StdnumNotInitializedError, also exported from the /browser subpath.

Supported registries

| Subpath | Jurisdiction | Registry | | --------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------- | | /ares | Czech Republic | ARES — public open API | | /brreg | Norway | Brønnøysundregistrene — public open API | | /denue | Mexico | INEGI DENUE — official establishment / economic-unit API; token required | | /sudreg | Croatia | Sudski registar — public company lookup | | /zefix | Switzerland | Zefix — public commercial-register search API |

More jurisdictions land per-PR; see the package README on the main branch for the current list.

Design notes

Every registry client follows the same contract:

  • A lookupBy<Id>(id, options?) function that returns the parsed domain entity or null when the identifier is not found.
  • A searchByName(name, options?) function that returns a flat list of results.
  • Tagged errors (<Registry>APIError, <Registry>ValidationError, <Registry>RequestError, <Registry>TooBroadError) so callers can branch on failure mode.
  • Pure parsers exposed alongside the client so consumers can ingest cached or mocked raw payloads without hitting the network.

Adapters also export toNormalizedEntity and toNormalizedSearchResult projections where a domain model is available. Each optional normalized field is a discriminated value: it contains data when available, or records that the field was not loaded or is not supported by that adapter. These states cannot overlap.

Tests use captured fixtures and mocked HTTP responses so the suite stays deterministic and offline-safe.

License

Apache-2.0