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-spec

v0.2.0

Published

OpenAgenda v3 public API — OpenAPI 3.1 contract (source of truth for SDK, MCP and docs)

Downloads

447

Readme

@openagenda/api-spec

The OpenAPI 3.1 contract of the OpenAgenda v3 public API — the single source of truth from which the rest of the v3 ecosystem is derived:

Usage

import { readFile } from 'node:fs/promises';

const specPath = import.meta.resolve('@openagenda/api-spec/openapi.yaml');
const spec = await readFile(new URL(specPath), 'utf8');

Or point any OpenAPI tooling at node_modules/@openagenda/api-spec/openapi.yaml.

Scripts

  • yarn validate — structural validation: every $ref resolves and every example/examples entry validates against its schema (ajv, 2020-12).
  • yarn lint@redocly/cli lint over the contract.

Conventions

The contract is spec-first: endpoints are designed here before they are implemented, and the implementation is tested against it. Changes must keep yarn validate green; the SDK is regenerated from it (yarn workspace @openagenda/api-client generate:check guards drift).