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

@cto.af/ca

v2.6.4

Published

Testing-only Certificate Authority (CA) for your local development environment ONLY. This is in no way suitable for production of any kind.

Readme

@cto.af/ca

Testing-only Certificate Authority (CA) for your local development environment ONLY. This is in no way suitable for production of any kind.

This package will automatically create new keypairs as needed, with the CA cert lasting a year by default and the leaf certs 3 days by default.

Currently, there is NO SECURITY for the private keys. These should be stored in an OS-specific keychain one day.

Installation

npm install @cto.af/ca

API

Full API documentation is available.

Example:

import {createCert} from '@cto.af/ca';
import {createServer} from 'node:tls';

// This reads and writes files from a user-scoped config directory for
// the CA cert and cwd()/.cert for the certificate.
const {key, cert} = await createCert({
  host: 'foo.local', // Default: 'localhost'
});
const server = createServer({key, cert}, () => {
  // Handle connection
});

On the client side, a mechanism is provided to override some of the TLS internals of node so that fetch will work correctly.

Example:

import {whileCAtrusted} from '@cto.af/ca/client';

const fetchResult = await whileCAtrusted(
  {}, // CA options, or a PEM-encoded string with the CA cert.
  () => fetch('https://localhost:8001')
);

CLI

A rudimentary CLI is provided.

Usage: cto-af-ca [options] [command]

Options:
  -d,--dir <DIRECTORY>  Directory for CA certs (default:
                        "[User config directory]/@cto.af/ca-nodejs")
  -h, --help            display help for command
  -q,--quiet            Less verbose
  -v,--verbose          More verbose

Commands:
  cert [options]        Create a cert signed by the CA
  create [options]      Create a CA certificate
  dir                   Show directory for certs
  list                  List exising certs by subject
  rm <SUBJECT>          Remove a CA cert by subject
  help [command]        display help for command

Build Status codecov