Pet library
Published packages, read live from the library service's public index. A package is
Evolving when its pet.json carries an object-valued
evopet block, and Stock when it does not — the same test the
desktop app makes, in the same words. Nothing on this page is cached, counted by hand, or
drawn without the API having sent it.
Reading the library index…
The library could not be reached
No pets are listed, because the index did not answer. This is shown instead of an empty library so the two can never be confused.
A site on a different origin than the service cannot read it: the library sends no CORS headers, so the deployment has to put this site and the service on one origin, or give the service an allowlist. That decision is still open.
No pets published yet
The index answered, and it is empty: nobody has published a package to this service. That is the honest state of a young library, not an error.
No pets match
Every published pet was filtered out by the current search or capability filter.
What this page deliberately does not do
- No publishing. There is no upload form, no key field and no account here. Publishing goes through the service's own bearer-key endpoint, run by whoever owns the key.
- No install button.
petdex://install links still resolve to petdex.dev, and the desktop app's catalogue manifest is a compiled constant, so a link here would imply an install path that does not exist yet. - No gauges. The page shows what a published package is, not how anyone's pet is doing: a pet's ledger is per-profile and stays on the machine that grew it.
- No counters of our own. Every count on this page comes from the index's
own
totalandcapableTotalfields.