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

@cesteral/contract-schema

v1.3.0

Published

Canonical governance-contract surface (annotations, manifest, dry-run, contractId) shared by Cesteral MCP servers and governance

Downloads

955

Readme

@cesteral/contract-schema

The canonical governance-contract surface for the Cesteral MCP ecosystem — the single source of truth shared by the MCP servers (mcp-open-advertising) and the governance layer (cesteral-intelligence).

Where @cesteral/contract-hash owns how a tool definition is hashed, this package owns the shape of what gets governed:

  • Tool annotations — the cesteral.* namespace, in two deliberately different-strictness faces:
    • Authoring types (CesteralToolAnnotations, CesteralEntityWriteToolAnnotations, …) — the strict contract MCP-server authors write against with satisfies.
    • Validation schema (cesteralAnnotationSchema, parseCesteralAnnotation) — the loose shape governance parses untrusted tool lists with, so it can apply contract-promise checks (requiresValidation, …) as specific admission reason codes rather than a generic parse failure.
  • Canonical enumsCESTERAL_WRITE_OPERATIONS / writeOperationSchema and canonicalEntityKindSchema / CanonicalEntityKind.
  • contractId derivationderiveContractId, safeDeriveContractId, slugSchema.
  • Governed response shapesdryRunResultSchema, normalizedEntitySnapshotSchema, dispatchedCapabilitySchema, effectDryRunResultSchema, and their TS mirrors.
  • Release attestation manifestcesteralManifestSchema.
import {
  parseCesteralAnnotation,
  deriveContractId,
  cesteralManifestSchema,
} from "@cesteral/contract-schema";

const parsed = parseCesteralAnnotation(tool.annotations?.cesteral);
if (parsed.success) {
  // parsed.data.contractId === deriveContractId(slug, slug, version)
}

Each TS authoring type and its Zod validation mirror are pinned together by the package's type-tests — the two faces cannot silently drift, and any value satisfying an authoring type is guaranteed to parse under the schema.