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

@anymail/sdk

v0.1.0

Published

Official TypeScript/JavaScript client for the AnyMail Developer API (/api/v1). Generated from the server's own OpenAPI spec - see ../README.md.

Readme

@anymail/sdk (TypeScript/JavaScript)

Official TypeScript/JavaScript client for the AnyMail Developer API (/api/v1).

src/generated/types.ts is generated fresh from ../openapi.json by openapi-typescript - see ../scripts/generate-spec.ts and ../README.md. src/client.ts, src/webhooks.ts, and src/index.ts are the hand-written files in this package.

Install

npm install @anymail/sdk

Self-hosted alternative

If you'd rather install straight from an AnyMail deployment instead of npm (or npm publishing isn't turned on for this deployment yet - see ../README.md "Publishing"), npm can install directly from a tarball URL - no filename-detection trick needed here, unlike pip:

npm install https://anymail.tech/api/sdk-artifacts/typescript

Usage

import { AnyMailClient, unwrapOrThrow } from '@anymail/sdk';

const client = new AnyMailClient({ apiKey: 'am_...' }); // baseUrl defaults to https://anymail.tech/api/v1

// Full type inference for every endpoint via client.api (openapi-fetch), no per-endpoint code:
const { data, error } = await client.api.GET('/mail-servers/{id}', { params: { path: { id: 'ms_...' } } });

// Or throw-on-error, matching AnyMail's own {code, message} error contract:
const { user } = unwrapOrThrow(await client.api.GET('/me'));

const { message } = unwrapOrThrow(
  await client.api.POST('/inboxes/{id}/messages', {
    params: { path: { id: 'inb_...' } },
    body: { to: '[email protected]', subject: 'Hi', body: 'Hello!' }
  })
);

client.api is a real openapi-fetch client typed against the generated paths - every Developer API endpoint (including ones added after this README was written) is reachable through it with full type inference. unwrapOrThrow is a small, generic helper (not tied to any one endpoint) that turns a {data, error} result into data, or throws AnyMailApiError carrying the server's status/code/message/details.

Webhook signature verification

import { verifyWebhookSignature } from '@anymail/sdk';

if (!verifyWebhookSignature(rawBody, req.headers['x-anymail-signature'], webhookSecret)) {
  return res.status(400).end();
}

rawBody must be the exact string of the received request body, read before any JSON parsing - see the function's docstring. Node-only (uses node:crypto), which is fine since webhook verification always runs on the receiving server, never in a browser. This helper is unrelated to client.api and works even if you're not otherwise using this SDK to call the API.

Regenerating

See ../README.md "Regenerating locally".