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

@circleci/trusted-publishing-example

v1.0.193

Published

Just a hello world package to publish with trusted publishing via cci

Readme

@circleci/trusted-publishing-example

A minimal example package showing how to publish to npm from CircleCI using trusted publishing, with no long-lived NPM_TOKEN.

For the full walkthrough, see Publish to npm.

Project Structure

  • build.sh - Sets a dynamic version (MAJOR.MINOR.<CIRCLE_BUILD_NUM>) on package.json
  • index.js - The package's one function: helloWorld
  • index.test.js - Tests, runnable with npm test
  • ../.circleci/npm-publish.yml - CircleCI pipeline

How It Works

  1. CircleCI runs the publish job on push to main.
  2. The job mints an OIDC token (circleci run oidc get --claims '{"aud": "npm:registry.npmjs.org"}') and exports it as NPM_ID_TOKEN.
  3. npm publish detects NPM_ID_TOKEN and exchanges it for a short-lived publish token.

The trusted publisher is configured on npmjs.com under the package's Settings → Trusted Publishing tab and is bound to the trusted-publishing-guard CircleCI context, which has an expression restriction limiting it to main. A staging workflow on non-main branches is included to demonstrate that the lockdown rejects publishes from other branches.