How Packages Get Published

You don’t publish packages to registry.pure.dev yourself — there’s no publish token or npm publish workflow for customers. Everything in the registry is published by Pure.

How it works

1. Every package not published to Pure’s registry is transparently proxied from the real npm registry — see Proxy behaviour. This is the default for everything.
2. Pure watches npmjs.org for new package versions and, for packages it has tested and certified as byte-identical to their real npm behavior, compiles them to native .node modules.
3. Those certified builds are published to registry.pure.dev automatically. Nothing changes on your end — npm install for a certified package resolves to the compiled version instead of the proxied one, with the same name and version you’d install from npmjs.org.

If a package isn’t certified yet, npm install still works — it’s served through the npm proxy like any other package.

Why we don’t accept customer publishes

Every package in the registry has been tested for byte-identical behavior against its real npm counterpart. Allowing arbitrary publishes would break that guarantee, so publishing is restricted to Pure’s own automated pipeline.