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

@zweer/publish-dummy-package

v0.2.1

Published

A CLI tool to publish dummy packages to npm for OIDC provenance setup in monorepos

Readme

@zweer/publish-dummy-package

A CLI tool to publish dummy packages to npm for OIDC provenance setup in monorepos.

When using npm OIDC (provenance) publishing from CI (e.g., GitHub Actions), the package must already exist on npm. This tool scans your monorepo, finds unpublished packages, and publishes a minimal placeholder so you can then configure OIDC trusted publishers.

Installation

npm install -g @zweer/publish-dummy-package

Usage

CLI

# Scan packages/ and publish any missing packages
publish-dummy-package

# Custom packages directory
publish-dummy-package --packages-dir ./libs

# Dry run (no actual publish)
publish-dummy-package --dry-run

# Restricted access (scoped private)
publish-dummy-package --access restricted

Options

| Option | Default | Description | | :--- | :--- | :--- | | --packages-dir <PATH> | ./packages | Path to the packages directory | | --access <ACCESS> | public | npm publish access level (public or restricted) | | --dry-run | false | Perform a dry run without publishing |

Programmatic API

import {
  checkNpmLogin,
  discoverWorkspacePackages,
  publishDummyPackages,
} from '@zweer/publish-dummy-package'

// Check npm login
const username = checkNpmLogin()

// Discover packages
const packages = discoverWorkspacePackages('./packages')

// Publish all unpublished packages
const results = publishDummyPackages({
  packagesDir: './packages',
  access: 'public',
  dryRun: false,
})

Prerequisites

  • You must be logged in to npm (npm login)
  • Each package must have a valid package.json with a name field

License

MIT