DocsOverview
    nextpm

    Docs

    How to install from nextpm, publish to it, and keep packages private.

    Start

    Getting startedPoint your client at nextpm, sign in, publish a package, and install it.

    Guides

    PublishingPublish from a terminal with a passkey for each change, or from GitHub Actions with no stored token.Private registriesGive your scopes their own host, readers, and search index, off the public registry.Release sealsEach release has a seal, a picture of its tarball hash. Two releases with the same bytes have the same seal.

    Reference

    API referenceEach route of the registry, the rules that each route applies, and the features that are not available yet.

    nextpm is an npm registry. npm, pnpm, Bun, and Yarn use it with no plugins.

    The examples use example.com for the website and registry.example.com for the registry host.

    Common tasks#

    How nextpm differs from npm#

    • You sign in with a passkey, and your passkey approves each publish and each other change. The registry never asks for a one-time code.
    • No token can publish alone. CI publishes with trusted publishing, and by default a maintainer approves each release.
    • Readers are free. Private packages cost per person who publishes. See Pricing.
    • A private registry has its own host and its own search index.
    • Each release has a seal: a picture of its tarball hash.