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

@roger-protocol/specs

v0.2.2

Published

Roger API specifications and standards

Readme

The Roger Protocol Specifications

This repository contains the Roger Protocol Specifications.

We are open to contributions. See CONTRIBUTING.md or more details.


1. Project Structure

The Roger Protocol Specifications repository uses the following folder structure:

  • /docs: Documentation files that will be parsed by Fumadocs. This folder uses the Fumadocs Page Tree structure, and uses the .mdx format to write documentation files.

  • /src: this contains the official protocol definitions written as type-safe Zod schemas.

    • /src/shared: the shared folder contains all constants and logic that can be safely shared accross core and features domains.
    • /src/core: the core folder contains all of the non-optional, independent, features that all specification consumers must implement.
    • /src/features: the features folder contains all of the optional features that the specification consumer may implement. Note: TypeScript files must be located under domain folders inside of /src/features (e.g. /src/features/my-feature/index.ts)

2. Installation & Usage

The Roger Protocol Specifications package is available on npm under the Apache-2.0 license. The npm package includes an openapi.json file, which can also be found in the asset section of any GitHub release.

2.1. JavaScript / TypeScript Setup

To use the Roger Protocol Specifications package inside of your JS/TS project, ensure you have Node.js installed and run the following command:

npm i @roger-protocol/specs

Then, import Zod schemas in your JS/TS files

import { loginBodySchema } from "@roger-protocol/specs/auth"
import { coolFeatureBodySchema } from "@roger-protocol/specs/feature"

2.2. Non-JavaScript Ecosystems (Go, Rust, Luau, ...)

If you are implementing the Roger Protocol in another programming language than JavaScript/TypeScript, you can use the compiled openapi.json to generate type-safe clients with tools like openapi-generator.

The openapi.json file can be found in multiple locations:

  • In the npm package:
import openapiJson from '@roger-protocol/specs/openapi.json';
  • In the node_modules folder: Located under ../node_modules/@roger-protocol/specs/dist/openapi.json after install
  • Directly in GitHub: Attached as a static asset under the GitHub Release of your choice