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

trustci

v0.2.0

Published

Bulk-register npm Trusted Publishers (npm trust) across all public packages in a monorepo. Supports GitHub, GitLab and CircleCI.

Readme

trustci

Bulk-register npm Trusted Publishers across all public packages in a monorepo with a single command. Wraps npm trust and supports GitHub Actions, GitLab CI/CD, and CircleCI.

Setting up trusted publishing one package at a time is tedious in a monorepo. trustci detects your workspace, finds every public package, and runs the right npm trust <provider> … for each.

Requirements

  • npm 11.5.1 or later (for npm trust)
  • Node 22.14.0 or later

Usage

# Preview the commands without running anything (recommended first step)
npx trustci --dry-run --provider github --repo me/repo --file release.yml --allow-publish

# Actually register (asks for confirmation unless -y)
npx trustci --provider github --repo me/repo --file release.yml --allow-publish

# List current trusted publishers for every public package
npx trustci list

Providers

| Provider | Required flags | Optional | | ---------- | ---------------------------------------------------------------------------------------------- | --------------- | | github | --repo <owner/repo> --file <workflow> | --env <name> | | gitlab | --project <group/project> (or --repo) --file <workflow> | --env <name> | | circleci | --org-id --project-id --pipeline-definition-id --vcs-origin <url> | --context-id (repeatable) |

At least one of --allow-publish / --allow-stage-publish is required.

# GitLab
npx trustci --provider gitlab --project me/repo --file .gitlab-ci.yml --allow-publish -y

# CircleCI (vcs-origin must include the protocol)
npx trustci --provider circleci \
  --org-id <uuid> --project-id <uuid> --pipeline-definition-id <uuid> \
  --vcs-origin https://github.com/me/repo \
  --context-id <uuid> \
  --allow-publish

Common options

| Flag | Description | | ------------------------ | --------------------------------------------------- | | --dry-run | Print the npm trust commands without executing. | | --only <name-glob> | Only include packages matching (repeatable). | | --exclude <name-glob> | Exclude packages matching (repeatable). | | -y, --yes | Skip the confirmation prompt (and npm's). | | -h, --help | Show help. | | -v, --version | Show version. |

Workspace detection

Patterns are read from the first of:

  1. pnpm-workspace.yaml (packages:)
  2. package.json (workspaces)
  3. lerna.json (packages)

Packages marked "private": true are always excluded. On a real (non-dry) run, packages not yet published to the registry are skipped with a warning.

Development

Built with Bun, ships zero runtime dependencies, and the published artifact is plain Node-compatible JS.

bun install
bun test
bun run build   # -> dist/cli.js (npx entry point), via `bun build --target node`

License

MIT