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

@e18e/setup-publish

v1.1.0

Published

A CLI to help with building publish workflows.

Readme

@e18e/setup-publish

npm version License: MIT

🚀 A tiny CLI to assist with setting up GitHub workflows for publishing packages to npm.

📦 Install

npm install -g @e18e/setup-publish

Or you can use npx:

npx @e18e/setup-publish

🚀 Usage

# If installed globally
setup-publish

# Or using npx
npx @e18e/setup-publish

🛠️ Features

  • Granular permissions - Each workflow step has minimal required permissions
  • SHA-pinned actions - GitHub actions referenced by commit SHA for security
  • Install scripts disabled - Prevents malicious package install scripts from running
  • Separated jobs - Build and publish run as independent jobs for better isolation
  • Secure publish - Publish job only uploads pre-built artifacts, no external code execution
  • Staged publishes - Releases are staged on npm for manual approval before going live (where supported by the template)

⚙️ Options

By default, the CLI runs in interactive mode, prompting you for configuration options. You can also provide options directly via the command line with --no-interactive to skip the prompts entirely.

| Option | Description | Default | Available Values | |--------|-------------|---------|------------------| | --output <path> | Output path for the generated workflow file | .github/workflows/publish.yml | Any valid file path | | --template <name> | Template to use for workflow generation | default | default - Manual GitHub release managementchangelogithub - Automated changelog with changelogithubchangesets - Automated releases with changesets | | --env <env> | GitHub environment for deployment protection | none | Any environment name | | --pm <name> | Package manager to use in the generated workflow | npm | npm, pnpm, bun | | --interactive | Run CLI in interactive mode | true | boolean |

📚 Examples

Interactive Mode (Default)

setup-publish

Non-Interactive Mode

# Generate workflow with changesets template
setup-publish --no-interactive --template changesets

# Custom output path with GitHub environment
setup-publish --no-interactive --output .github/workflows/release.yml --env production

# Use changelogithub template with custom environment
setup-publish --no-interactive --template changelogithub --env staging

📋 Templates

🎯 Default

Manual GitHub release management - this is the most basic setup, allowing you to create releases manually via GitHub's interface.

📝 Changelogithub

Automated changelog generation using changelogithub - ideal for projects following conventional commits.

🔄 Changesets

Automated releases with changesets - great for monorepos and coordinated releases.

[!NOTE] Changesets does not yet support npm staging, so releases publish directly.

Sponsors

📄 License

MIT