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

devcontract

v0.1.0

Published

Evidence-backed engineering contract and guided AI workflows for git repos

Readme

devcontract

Evidence-backed Team Engineering Contract + guided AI workflows (Understand, Build), served over MCP stdio so Grok, Claude Code, Codex, Kiro, and Cursor share the same tools.

npx -y devcontract

Requires Node.js 22+ and git on PATH. Build plans need XAI_API_KEY (xAI / SpaceXAI). Understand is deterministic and works without a key.

Status

v0.1.0. Working now:

  • npx -y devcontract — MCP stdio with dev.understand
  • devcontract contract compile — Team Engineering Contract from git artifacts
  • devcontract understand <path-or-ticket> — cited git history (no API key)

Still stubbed: init, build, approve, run.

Product overview: docs/PRODUCT.md
Design: docs/DESIGN.md

MCP clients

Claude Code / Cursor — .mcp.json or .cursor/mcp.json:

{
  "mcpServers": {
    "devcontract": {
      "command": "npx",
      "args": ["-y", "devcontract"]
    }
  }
}

Codex / Grok — project MCP config, command = "npx", args = ["-y", "devcontract"], startup_timeout_sec = 60.

Kiro — best-effort .kiro/settings/mcp.json (same JSON shape).

Put XAI_API_KEY in the host environment. Do not commit it.

CLI

npx -y devcontract              # MCP stdio (default)
npx -y devcontract --help
npx -y devcontract init
npx -y devcontract contract compile
npx -y devcontract understand <path-or-ticket>
npx -y devcontract build <ticket>
npx -y devcontract approve <runId>    # TTY only; not an MCP tool
npx -y devcontract run <runId> [--resume]

Develop

npm install
npm test
npm run build

License: Apache-2.0