Sign In

@moshcoder/moshpit-registry

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@moshcoder/moshpit-registry

Client for the Moshpit registry — resolve names, read key pins, list endings. Cached, coalesced, bounded, and clear about which failures are answers.

Source
npmnpm
Version
0.1.0
Version published
Weekly downloads
7
-73.08%
Maintainers
1
Weekly downloads
 
Created
Source

@moshcoder/moshpit-registry

Client for the Moshpit registry — resolve names, read key pins, list endings.

npm i @moshcoder/moshpit-registry
import { createRegistry } from "@moshcoder/moshpit-registry";

const registry = createRegistry();
await registry.resolve("blue.eggs");   // where it points, and who holds the ending
await registry.pins("blue.eggs", "tls"); // the keys it may present
await registry.tlds();                  // every ending claimed

Why it is a package

Three clients had grown independently — the resolver bridge, the pinning proxy, and the browser extension. They agreed on the endpoints and disagreed on everything that matters under load: which failures are cacheable, whether two simultaneous lookups become one request, how long to wait before giving up.

The distinction it is careful about

A definite no is not an outage. A 400 or 404 is an answer — the name is malformed, or nobody has published a key — and is cached for as long as a real answer. A timeout or a 500 is not, and is remembered only briefly so an outage is not amplified into a flood.

A client that treats them alike either fails closed forever or fails open once, and the second is how a namespace gets quietly defeated.

An empty pin list is "no key published", not "any key will do".

What it does under load

  • Bounded timeouts — this sits in front of navigation, so a slow registry becomes a fast no rather than a hang
  • Cached, so a page of names is not a page of requests
  • Coalesced, so a client retrying a query it thinks was lost becomes one request rather than N
  • Failures return null instead of throwing, because every caller here is deciding whether to connect, not whether to crash

CLI

moshpit-registry resolve <name>       where a name points, and who holds it
moshpit-registry pins <name> [kind]   the keys a name may present (tls | mtp)
moshpit-registry tlds                 every ending claimed

--registry URL    a self-hosted pit
--json            raw JSON instead of a summary
$ moshpit-registry resolve california.oranges
california.oranges
  ending held    yes
  name minted    yes
  points at      nothing yet

License

MIT.

Keywords

moshpit

FAQs

Package last updated on 31 Jul 2026

Related posts