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

@oprt/manifest

v0.4.0

Published

OPERATOR's machine-readable contract for coding agents and tools: every component's props, option values and nesting rules, usage guidance and six complete recipes, with Zod schemas to validate it.

Readme

@oprt/manifest

The machine-readable contract of the OPERATOR design system: what every component accepts, how components fit together, and six complete working screens. It is written for coding agents and the tools that serve them, and it is released at the same version as @oprt/react.

An app that only renders the components does not need this package.

Which file to use

| File | What it holds | Use it | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | | components.json | Every component's props, option values, slots, nesting rules and example; the composition rules; a summary of each recipe (≈130 KB) | Give it to an agent | | guidance.json | Which component to choose and what to use instead, what each option value is for, and the house rules as "use this, not that" pairs, and the setup a project needs (setup) | With components.json, when choosing components | | agent-prompt.md | A system prompt that tells an agent how to work with the contract | As the agent's instructions | | manifest.json | Everything in components.json, plus the complete source of the six recipes (≈850 KB) | Only to read or copy a recipe's source | | schema.json | The JSON Schema of manifest.json | To validate a manifest in any language |

The six recipes are Asset Management, Operations Map, Maintenance Planning, Facility Monitoring, Incident Response and Communications Console. guidance.json is checked against the contract when it is built, so the two cannot drift apart.

import { readFileSync } from "node:fs";
import { createRequire } from "node:module";

const require = createRequire(import.meta.url);
const components = JSON.parse(
  readFileSync(require.resolve("@oprt/manifest/components.json"), "utf8"),
);
components.components.Button.props.variant.values; // ["primary", "secondary", …]

Validating

The package's entry exports the Zod schemas and their types:

import { ComponentSchema, ManifestSchema, type Component } from "@oprt/manifest";

const result = ManifestSchema.safeParse(JSON.parse(text));
if (!result.success) console.error(result.error.issues);

ComponentSchema, PropSchema, SlotSchema, PatternSchema, CompositionRuleSchema, ComponentsManifestSchema and GuidanceSchema are exported beside ManifestSchema, each with its type.

The same contract, served

@oprt/cli answers from this contract without reading files: oprt init writes an agent's instructions into AGENTS.md, CLAUDE.md or Cursor's rules; search and component look things up; check reports invalid values, unknown exports and forbidden nesting in a project's code; mcp serves the lookups and the check over the Model Context Protocol. See oprt.dev/docs/agents.

License

MIT.