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

@yozz.app/x509

v0.1.3

Published

Strict DER, X.509 certificate decoding and RFC 5280 path validation in TypeScript, with a compiled trust store. Runs in Node and browsers, no native code.

Readme

@yozz.app/x509

Strict DER, X.509 certificate decoding and RFC 5280 path validation in TypeScript, with a compiled trust store built from curl's cacert.pem and NSS's distrust cutoffs. It is the certificate half of @yozz.app/tls.

  • decodeDer / decodeCertificate: total parsers that reject rather than guess.
  • YOZZ_VALIDATOR: hostname matching, chain building, signature verification (WebCrypto), validity, name constraints, key usage.
  • ROOT_BUNDLE: the shipped anchors, so a browser has a root store.
  • Gate: x509-limbo, 902/902 accepts and 8827/8837 rejects, every over-accept attributed.
pnpm add @yozz.app/x509
import { compileAnchors, ROOT_BUNDLE, SERVER_AUTH, YOZZ_VALIDATOR } from '@yozz.app/x509';

const result = await YOZZ_VALIDATOR.validatePath({
  peerCertificateDer: leafDer,
  untrustedIntermediateDer: intermediatesDer,
  trustAnchors: compileAnchors(ROOT_BUNDLE).source,
  validationTime: new Date(), // never the clock implicitly; every limbo case pins this
  expectedPeerName: { kind: 'dns', value: 'imap.example.com' },
  requiredKeyUsages: [],
  requiredExtendedKeyUsages: [SERVER_AUTH],
  maximumIntermediateCount: null,
});
// { ok: true, path } or { ok: false, reason } naming the check that refused

src/index.ts is the whole public API and says why each export exists; the request and result types are in src/validator.ts. The source is in fishballapp/yozz, which takes issues but no pull requests.

MIT.