About rgstr
rgstr is dns for packages: a public registry of who has claimed a package name on npm and PyPI, and an install endpoint that resolves claimed names to the real package. It is built and operated by ComputeSDK (Snelling, LLC).
What it does
Every npm and PyPI name has a page at /registry/<name> that says who has claimed it (or that nobody does), how far that was checked, and where installs of it are served from. Three trust levels: unclaimed (nobody has claimed the name), claimed (a maintainer applied, put the rgstr badge in a README rgstr reads, and a person approved the claim), verified (claimed, and the organization also paid for identity verification).
Pointing npm or pip at rgstr once makes every install of a claimed name resolve to the package its claimant publishes, with copies ranked below it. Unclaimed names fall through to registry.npmjs.org and pypi.org unchanged, so there is nothing to lose by turning it on.
What it is not
Not a mirror. rgstr stores no package files. It fetches the listing from the index that publishes the package, passes it through with download links pointed at rgstr, and answers each download with a redirect to the real file on the index. The bytes you install are the index's bytes.
Not a scanner. rgstr does not read code for malware or judge a package's quality. It answers one question: is this name claimed, by whom, and how was that proved.
Not affiliated with npm, Inc. or the Python Software Foundation. Package data shown on rgstr.org comes from registry.npmjs.org and pypi.org.
Who runs it
rgstr.org is a product of ComputeSDK, the compute platform for agents, operated by Snelling, LLC. The registry site, its API and the rgstr CLI (https://github.com/computesdk/rgstr) are maintained by the same team; the CLI is open source.
A person reviews every claim; a found badge is evidence, not approval. Disputes go by email (see Contact), are not shown on the public page, and both sides are told the decision. The long answers, including what happens when rgstr.org is down and what we log, are on Why rgstr.
Cost
Looking names up, searching, installing through rgstr, and claiming the names you maintain are free and need no account for lookups and installs. A claim needs a sign-in (GitHub, Google or email, self-serve; rgstr login does it from the terminal) or the no-account form at /registry/claim. The one paid thing is identity verification of an organization, which raises its claimed names from claimed to verified; no claim needs it.
For agents
Every page on rgstr.org has a Markdown rendering: send Accept: text/markdown. The API is public and documented at /registry/-/api with an OpenAPI 3.1 spec at /openapi.json; /llms.txt is the short map of all of it.