Staged Publishing for NPM Packages

May 20, 2026 · 11:08 PM UTC ·2 min read · 0 reactions · 0 comments · 25 views

TL;DR · WeSearch summary

Staged publishing for npm packages introduces an approval step before packages are made public. Maintainers must review and approve staged packages using two-factor authentication. This process is designed to enhance security and ensure quality control before package versions are released on the npm registry.

Key facts

▪Staged publishing requires npm CLI version 11.15.0 or later and Node version 22.14.0 or higher.
▪Packages must already exist on the npm registry to be staged, and 2FA must be enabled on the npm account.
▪Maintainers can review staged packages using the CLI or npmjs.com before approving them for public release.

How this story was covered

6 outlets in our directory ran this story, first to last over 2 days. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 5

▪ Staged publishing and new install-time controls for NPM — The GitHub Blog
▪ Staged publishing for npm packages | npm Docs — r/programming
▪ Staged publishing for npm packages | npm Docs — r/javascript
▪ Staged publishing for npm packages | npm Docs — r/cybersecurity
▪ Publishing to npm Securely — r/node

About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

All Hacker News (Newest) coverage →

Original article

Npmjs

Read full at Npmjs →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Npmjs
Canonical URL	https://docs.npmjs.com/staged-publishing/
Publication time	Wed, 20 May 2026 23:08:14 +0000
Retrieval time	2026-05-20T23:35:03.124Z
Last seen	2026-05-20T23:35:03.124Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	_g2-S962yhLJ · 8 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

Packages and modulesSecuring your codeStaged publishingStaged publishing for npm packagesTable of contentsHow staged publishing worksPrerequisitesStage a packageReview a staged packageUsing the CLIUsing npmjs.comApprove a staged packageUsing the CLIUsing npmjs.comUsing staged publishing with trusted publishersLearn moreStaged publishing adds an approval step before packages go live on the npm registry. Instead of publishing directly with npm publish, you can submit packages to a staging area with npm stage publish. A maintainer must then review and explicitly approve the staged package — with two-factor authentication (2FA) via the CLI or npmjs.com — before it becomes publicly available.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Npmjs.

Anonymous · no account needed

Discussion

0 comments