Publish from Bit, pnpm or npm. Every version is read, checked and tested before anyone installs it.
You with Bit · $ bit tag && bit exportAlready in use
Claude Codereads the API over MCPreadyRegistry log
The understanding layer
Because it understands the artifact instead of just storing it, every package becomes knowable — open one and see for yourself. A flat store never can.
Built for pnpm · friendly with npm
We built the deepest integration with pnpm — use the exact commands you already know, including batch-publishing an entire monorepo in a single request. Prefer npm? That works too. Either way, everything you publish becomes instantly reusable across your team and your AI.
One command publishes your whole monorepo — every package uploaded in a single request.
The pnpm creator
I know this probably won’t work for you at the moment because you want the packages to be in the “default registry” but you can publish to bit.cloud, which actually supports a batch publish. So you can run pnpm publish --batch -r and all your packages will be uploaded in one request.
The npm default registry can’t batch publish. Bit Registry can — and the pnpm author pointed a major OSS maintainer straight to it.
Secure by design
Bit maps how every component connects — so you can understand it, change it safely, and catch problems early.
Watch a change light up every component it touches — before it ships, not after.
On npm a prerelease is a dead string. Here it’s a living change — one version, joined to its impact, review, conversation, and release. The version number is the thread that connects every surface.
One version string — published, analyzed, discussed, installed, and released. npm can’t connect any of these. The Bit registry connects all of them.
Bit Registry
Free for open source. Native in pnpm, backed by the Bit graph. Don’t take our word for it — publish a package and feel the difference.