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

@openagenda/api-docs

v0.1.1

Published

OpenAgenda v3 API reference — static Scalar docs built from @openagenda/api-spec (source of truth: the OpenAPI contract).

Readme

@openagenda/api-docs

The OpenAgenda v3 API reference — a self-contained static Scalar site built from @openagenda/api-spec (the OpenAPI contract is the single source of truth).

The build output is fully static and zero-egress: the Scalar runtime is copied next to the page, the spec is inlined, and the OAuth playground talks directly to the OpenAgenda API and authorization server — nothing else is contacted at view time.

Scripts

yarn build     # render dist/ (index.html + standalone.js + openapi.yaml)
yarn dev       # rebuild on spec change + serve with live reload
yarn preview   # serve an existing dist/

OA_DOCS_ENV selects the target environment (prod, the default, or dev): API base URL and OAuth authorization server of the « try it » playground.

OAuth playground

The reference is executable: the playground uses OAuth 2.1 + PKCE (public client oa-api-docs) against the selected environment's authorization server, with read-only scopes. Tokens stay in the browser (persistAuth keeps them in localStorage on the docs origin only).