Reliverse

Package discovery · early preview

Package catalog

A home for discovering developer packages — starting with @reliverse tools, and designed to grow into a community registry.

Today this page shows a small, read-only index from our metadata API. Versions come from workspace manifests. Publication, installation and registry ownership have not been verified.

Explore the current index

2 packages in this view · workspace snapshot

  • @reliverse/dler-build

    Publication not verified

    Workspace version: 2.3.0

    View source manifest →

  • @reliverse/rdg-protocol

    Publication not verified

    Portable v0 contracts and decision helpers for Reliverse Deploy Gateway.

    Workspace version: 0.1.0

    View source manifest →

The API embeds an allowlisted build snapshot. Changes appear after it is rebuilt and redeployed; refreshing this page does not refresh an upstream registry.

Planned — not available yet

More than a package index

The goal is a full package-registry alternative to npmjs.com: first-party @reliverse packages and third-party packages from publishers using a Bleverse Account, with packages hosted by Reliverse as well as references to npm packages.

  • Community publishers

    Planned account-based publisher profiles and namespaces. Sign-in and publishing are not enabled in this preview.

  • A registry, not just links

    RPR is the intended package/version, verified-supply and registry substrate. Registry writes, downloads and install compatibility still need their own implementation and acceptance.

  • Connected discovery

    The intended api.reliverse.org integration and BGR federation will connect discovery across registries. A catalog reference will not pretend that an npm release is hosted or verified by Reliverse.