Registries

@agntn/registriesv0.3.0

Registries

Six registries, one class shape. Pick one to see its endpoints, its name rules and the traps.

Every adapter answers the same four calls: fetchPackage, fetchVersions, fetchDependencies and fetchMaintainers, plus a urls() builder for display links. What changes is the API it reads, what the registry calls latest, which version statuses it can report, and what ends up in metadata. The pages are short on purpose; the interesting part of each one is the gotcha list.

npm

One package document from registry.npmjs.org. Scopes in the namespace, deprecated as a status.

crates.io

Crate, versions, dependencies and owners across four endpoints. yanked as a status, docs.rs for docs.

PyPI

JSON API for metadata, Simple API for versions. Names normalized per PEP 503, extras become scopes.

RubyGems

Gem, versions, dependencies of each version and owners. yanked as a status, rubydoc for docs.

Packagist

One document per vendor/name with every version inside. php and ext-* requirements skipped.

Arch Linux

Official repos and the AUR behind one type, routed by namespace. One version per package, flagged out of date as deprecated.

Edit this pageorReport an issue

Explorer

The lookup page behind registries.agntn.dev that runs the library live, and what it does to be a good citizen.

npm

The npm registry API, one document per package, with scopes in the PURL namespace and deprecations as a version status.