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

@pulsate-dev/api-schema

v0.1.0

Published

OpenAPI schema for the Pulsate API

Readme

@pulsate-dev/api-schema

This package distributes the OpenAPI schema (schema.json) generated from the Pulsate API definitions.

It is intended to be consumed by API client generators (e.g. for pulsate-api-types) so that downstream projects can reference the latest API schema without manually copying the generated JSON file.

Usage

npm install @pulsate-dev/api-schema
import schema from '@pulsate-dev/api-schema/schema.json' with { type: 'json' };

Versioning

  • major/minor are bumped manually by maintainers when the API schema contains breaking changes.
  • patch is bumped automatically by CI whenever the generated schema changes.

Publishing

This package is published automatically by .github/workflows/publish-api-schema.yaml to the public npm registry. The schema is regenerated on every pull request and published only when it differs from the latest published version. Changes are never committed back to the repository.

Publishing uses npm's Trusted Publishing (OIDC): the workflow authenticates to npm using a short-lived token issued by GitHub Actions, so no long-lived NPM_TOKEN is stored as a repository secret. Each published version also carries npm provenance and a GitHub build provenance attestation, which let consumers verify the package was built from this exact workflow run (e.g. via npm audit signatures or gh attestation verify).

Because forked pull requests run with read-only GitHub Actions permissions, the OIDC token required to publish is unavailable to them, so this workflow cannot publish from an untrusted fork.

One-time setup (maintainers)

Before this workflow can publish, a maintainer must configure a Trusted Publisher for @pulsate-dev/api-schema on npmjs.com, pointing at:

  • Repository: pulsate-dev/pulsate
  • Workflow file: .github/workflows/publish-api-schema.yaml

If the package does not exist on npm yet, publish an initial version manually (npm publish --otp=... from a maintainer's authenticated machine, with 2FA) before wiring up the trusted publisher, since npm requires the package to already exist to attach a trusted publisher to it.