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

@licenseman/sdk

v1.0.0

Published

TypeScript client for the LicenseManager API: products, policies, customers, licenses, machines and releases.

Readme

LicenseManager TypeScript SDK

npm version npm downloads Types Publish License Documentation

The official TypeScript SDK for the LicenseManager API: issue, manage and validate software licenses. Fully typed, built on fetch: works in Node.js, Deno, Bun, edge runtimes and browsers.

Documentation · API reference · Changelog

Requirements

Node.js 18 or later, or any runtime with fetch.

Installation

npm install @licenseman/sdk

Usage

Create an API key in the LicenseManager app, then create a license after a sale:

import { Configuration, LicensesApi } from "@licenseman/sdk";

const licenses = new LicensesApi(
  new Configuration({ apiKey: process.env.LICENSEMANAGER_API_KEY }),
);

const license = await licenses.createLicense({
  productId: "x7Kp2QaZ",
  createLicense: {
    email: "[email protected]",
  },
});

And validate it from your application, which needs no API key:

import { LicensesApi } from "@licenseman/sdk";

const licenses = new LicensesApi();

const licenseToken = await licenses.validateKey({
  productId: "x7Kp2QaZ",
  validateKey: {
    key: "7KQ2M-X9ZPA-H4TRC-WN6EY-B3JDF",
    fingerprint: "4c:32:75:8f:9a:1e",
    version: "1.4.2",
  },
});

Authentication

Most endpoints take an organization API key: keep it on your servers. The endpoints your application calls directly, like validating a key, take no credentials or a token scoped to a customer, license or machine. See authentication and scoped tokens.

import { Configuration } from "@licenseman/sdk";

// With an API key, from your backend:
const configuration = new Configuration({ apiKey: process.env.LICENSEMANAGER_API_KEY });

// With a token scoped to a customer, license or machine:
const scoped = new Configuration({ accessToken: token });

Errors

Failed requests answer an error with a stable code to branch on, listed for each endpoint in the API reference. See errors.

import { ResponseError } from "@licenseman/sdk";

try {
  await licenses.getLicense({ id: "l3Nv8KwB" });
} catch (error) {
  if (error instanceof ResponseError) {
    const { error: details } = await error.response.json();
    console.error(error.response.status, details.code, details.message);
  }
}

Reference

Every method is documented, with its parameters and responses, in the docs folder:

| Class | Methods | | --- | --- | | LicensesApi | validateKey, listLicenses, createLicense, listCustomerLicenses, getLicense, deleteLicense, updateLicense, getLicenseStats, cancelLicense, sendLicenseKeys, getSigningKey | | PortalApi | getPortal, requestPortalLink, createPortalLink, createBillingPortalSession, sendPortalLink | | ProductsApi | listProducts, createProduct, getProduct, deleteProduct, updateProduct, resetProduct, uploadProductLogo, deleteProductLogo, getProductStats | | PoliciesApi | listPolicies, createPolicy, getPolicy, deletePolicy, updatePolicy | | CustomersApi | listCustomers, createCustomer, getCustomer, deleteCustomer, updateCustomer | | MachinesApi | listMachines, getMachine, deactivateMachine | | ReleasesApi | listReleases, createRelease, getRelease, deleteRelease, updateRelease | | TokensApi | createCustomerToken, createLicenseToken, createMachineToken | | EventsApi | listPolicyEvents, listLicenseEvents | | IntegrationsApi | getStripeIntegration, connectStripe, disconnectIntegration, updateIntegration, checkIntegration, listStripePrices, createStripeMapping, deleteStripeMapping, updateStripeMapping, getPaddleIntegration, connectPaddle, listPaddlePrices, createPaddleMapping, getSlackIntegration, authorizeSlack, deleteSlackConnection, updateSlackConnection, testSlackConnection |

Versioning

This SDK follows semantic versioning and is generated from the OpenAPI document of the API: each release is listed in the changelog. Please don't open pull requests, they would be overwritten by the next release: open an issue instead.

License

See LICENSE.