OSS Tanbou
View on GitHub

np — an interactive release CLI that checks branch, Git state, tests, 2FA, and dist-tags before npm publishing

OSS scale score 226.9OSS health 96Update pace 8 commits/30d
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
7,712
Primary language
JavaScript
License
MIT
Repository last updated
Sep 9, 2026

Overview

np calls itself “A better npm publish.” It combines release-branch checks, a clean working tree, unpulled-change detection, dependency reinstall, runtime compatibility, tests, version bumping, Git tags, pre-release dist-tag safety, 2FA, pushing, and GitHub release drafts into one interactive workflow. The latest stable release checked on September 23, 2026 is 12.1.1.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Run a structured set of pre-publish checks before changing the registry

np verifies the release branch, working tree, remote state, dependency installation, Node/npm compatibility, and tests before bumping versions, creating tags, and publishing. If publishing fails, it rolls the project back to its previous state.

Sources: [2]

Include 2FA, provenance, staged publishing, and release drafts in the workflow

It supports npm 2FA and enables 2FA on new packages by default, offers CI-only npm provenance, npm/pnpm staged publishing, GitHub release drafts, custom dist-tags, and alternate publish directories.

Sources: [2]

Best fit

Fits maintainers who want safer, consistent local npm package releases

It works well for libraries and OSS packages where maintainers want the same interactive checklist each time and can put np behind a shared release script in package.json.

Sources: [2]

Before adoption

12.1.1 fixes an OTP-prompt stream error

The patch fixes an OTP prompt failure that reported an invalid stream object, making it specifically relevant to publish flows using two-factor authentication.

Sources: [1]

Node.js 22+, npm 10+, and Git 2.11+ are required

Version 12.1.1 requires Node.js 22 or later, npm 10 or later, and Git 2.11 or later. Supported package managers include npm 10+, pnpm 11+, Bun, and both Yarn Classic and Berry.

Sources: [2][3]

Monorepos are unsupported and CI is not the primary target

The README explicitly lists monorepos as unsupported and says CI is not an ideal environment because np is designed as an interactive local release tool. Automated workspace releases may need a different release-management tool.

Sources: [2]

Use dry-run before the first real release

--dry-run shows the task plan without pushing or publishing remotely. It is a useful way to validate branch, test, dist-tag, and package-manager resolution before allowing a real release.

Sources: [2]

Official sources

  1. [1]np v12.1.1 release(2026-09-23)
  2. [2]np v12.1.1 README(2026-09-23)
  3. [3]np v12.1.1 package.json(2026-09-23)
  4. [4]np MIT license(2026-09-23)
Supplemental curator note

“A better npm publish.” np turns the checks around raw npm publishing into an interactive workflow. Version 12.1.1 fixes an OTP prompt issue, requires Node 22+/npm 10+, and is aimed at local package releases rather than monorepos or fully automated CI release systems.

Try it in 3 steps

  1. 1

    Check prerequisite versions

    np 12.1.1 requires Node.js 22+, npm 10+, and Git 2.11+.

    node --version && npm --version && git --version
  2. 2

    Install pinned np 12.1.1 globally

    Pin the release tool to the reviewed stable version.

    npm install --global np@12.1.1
  3. 3

    Run a dry-run from a package root

    Inspect the release task plan without pushing or publishing. Verify branch, tests, and dist-tag behavior before a real release.

    np --dry-run
Check the official README

Growth

Growth trends · Last 30 days

7,712 Stars

-1 (-0.0%)

Sep 5Sep 23

Development activity

Last 90 days · weekly

Commits (last 30 days)
8
Open PRs
0
Issues opened
5
Issues closed
7
PRs opened
5
PRs merged
5

Issues

5 / 7

Jun 23Sep 20
Issues openedIssues closed

Pull requests

5 / 5

Jun 23Sep 20
PRs openedPRs merged

Maintenance

Median first response
23 hr
Issue response rate
60% (3/5)

Based on up to the 100 newest issues opened by external users in the last 90 days. A first comment from an OWNER, MEMBER, or COLLABORATOR counts as a response; issues whose full comment history cannot be checked are excluded. The median and response rate update weekly.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub

GitHub Topics

  • npm
  • npm-package
  • publish
  • javascript
  • nodejs
  • npm-publish
  • yarn
  • cli
  • cli-app
Stars
7,712
Forks
311
Watchers
30
Open issues
4
Contributors
92
Primary language
JavaScript
License
MIT
Repository last updated
Sep 9, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.