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

@agentkitforge/contracts

v0.15.0

Published

Shared cross-service contracts for the AgentKitProject ecosystem: payload schemas, route builders, status enums, and the environment service manifest.

Readme

@agentkitforge/contracts

Shared cross-service contracts for the AgentKitProject ecosystem.

Every payload, route, status enum, and service URL that crosses a repo boundary is defined here first, then consumed by both sides of the seam:

| Seam | Provider | Consumers | |---|---|---| | Profile API (/profiles/*, /me) | agentkitprofile-infra | agentkitprofile-app, agentkitmarket-app, future Auto | | Forge ↔ Market (/api/forge/*) | agentkitmarket-app | agentkitforge-app | | Market backend (/admin/*, /users/*, /kits*) | agentkitmarket-infra | agentkitmarket-app |

Contents

  • src/profile.ts — public profile + publisher snapshot schemas, Profile API route builders, trusted headers
  • src/market.ts — submission/validation/review status enums, Forge submission payloads, Forge↔Market and Market-backend route builders
  • environments.json — canonical service base URLs per environment (the service manifest)
  • fixtures/ — JSON fixtures for non-TypeScript consumers (Forge's Rust tests) and provider contract tests

Rules

  1. New cross-repo fields/routes are added here before either side implements them.
  2. Providers and consumers both add a contract test against this package.
  3. Changing a published contract is a breaking change: bump the version and deploy both sides together.

TypeScript consumers install the published public npm package:

"@agentkitforge/contracts": "^0.2.0"

Rust consumers (and any non-TS consumer) assert request/response shapes against fixtures/*.json.