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

opensdd

v0.1.20

Published

The official OpenSDD (Open Spec-Driven Development) CLI, spec, and spec registry

Readme


An open protocol for spec-driven development with AI coding agents.

OpenSDD is a protocol and CLI for writing, sharing, and implementing behavioral specs — language-agnostic contracts that define what software should do, without dictating how. Specs are the source of truth. Code is derived from the spec, not the other way around.

How It Works

  1. Write a spec — Define behavior in markdown: contracts, edge cases, invariants.
  2. Implement it — Your AI agent reads the spec and produces an implementation that fits your project's language, framework, and conventions.
  3. Evolve it — When behavior needs to change, draft a changelog against the spec. Iterate until the changes are right, merge into the spec, then update the code.

Quick Example

# rate-limiter

> Token-bucket rate limiter.

## Behavioral Contract

### Core Behavior

Tracks request counts per client within a sliding time window.

- `allow(clientId)` MUST return `true` when the client is within their limit
- `allow(clientId)` MUST return `false` when the client has exhausted their limit
- The window MUST reset after `windowMs` milliseconds of no requests

### Invariants

- Total allowed requests per window MUST NOT exceed `maxRequests`

One spec, many implementations. Install it into an Express API and get middleware. Install it into a Python service and get a decorator. The spec is the reusable artifact — not the code.

Open Spec Registry

Specs can be published to the OpenSDD registry and pulled into any project:

opensdd install rate-limiter

Installation supports two formats:

  • Default mode — The spec is installed into the .opensdd.deps/ directory and managed through the full OpenSDD workflow: implementation tracking, conformance checking, deviations, and versioned updates.
  • Skill mode — The spec is installed as an agent skill across all supported coding agents (Claude Code, Codex CLI, Cursor, GitHub Copilot, Gemini CLI, Amp). Your agent gets the spec as contextual guidance without the formal SDD workflow. Use --skill on the install command, or set "installMode": "skill" in opensdd.json to make it the default.
opensdd install rate-limiter --skill

In either mode, your agent reads the spec and generates an implementation native to your stack.

Documentation

Development

See CONTRIBUTING.md for development setup and workflows.

License

MIT — see LICENSE for details.