npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

orator-api-description

v0.0.1

Published

A self-describing JSON API reference for Orator/Meadow servers: routes, schemas, example payloads and curl snippets, auto-derived from the compiled Meadow model and the live route table, so an agent or a developer UI can learn the API.

Readme

orator-api-description

A self-describing JSON API reference for Orator/Meadow servers. It serves the routes, request and response schemas, example payloads, and copy-pasteable curl snippets for an API, so an agent or a developer UI can learn the API instead of reverse-reading a web bundle. JSON, not YAML.

Most of it is auto-derived. Auto-CRUD routes generated by meadow-endpoints are described straight from the compiled Meadow model (the JsonSchema for request/response shapes, the DefaultObject for an example body, the presence of an IDCustomer column for tenant scoping). The live route table is the source of truth for what exists, so the description never drifts from what is actually mounted. Custom routes carry their method and path from that table plus a small annotation registry the host supplies for purpose, params and required entitlements (which cannot be read from code). A route with neither an entity match nor an annotation still appears, flagged Documented: false, so the inventory is always complete.

Routes

GET /<v>/API                     the inventory (filter with ?entity= ?method= ?kind= ?q= ?path=)
GET /<v>/API/Entities            entity index (name, primary key, tenant-scoped)
GET /<v>/API/Entities/:Entity    one entity's columns + request schema + example record
GET /<v>/API/Guides              guide index (key, title)
GET /<v>/API/Guides/:Key         one guide's markdown body

Use

const libApiDescription = require('orator-api-description');

libApiDescription.mount(pServiceServer, {
    Model: compiledMeadowModel,            // { Tables: { <Entity>: { MeadowSchema: { Schema, JsonSchema, DefaultObject, ... } } } }
    RouteProvider: () => liveRoutes,       // [ { method, path } ] -- e.g. off the router; falls back to introspection
    Annotations: annotationRegistry,       // { "GET /1.0/Account/Me": { Summary, Description, PathParams, QueryParams, Auth, ExampleRequestBody } }
    Guides: guides,                        // [ { Key, Title, Body } ]
    ExcludedEntities: { Account: true },   // entities with no auto-CRUD
    Version: '1.0',
    BaseURL: 'https://your-host',
    AuthGate: (pRequest) => isAuthenticated(pRequest)   // return truthy to allow; omit for public
});

The core (source/API-Description-Builder.js) is pure -- it takes plain data and returns plain objects, with no Orator, Fable or filesystem dependency -- so it is trivially testable and reusable. The mount adapter is a thin HTTP layer over it.

License

MIT