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

@10up/relay-schemas

v0.4.0

Published

Shared JSON Schemas for Relay content (PRD, notebook, document, asset, path allowlist) consumed by the Relay Cloud MCP server and Relay utilities

Downloads

119

Readme

@10up/relay-schemas

Shared JSON Schemas for content stored in Relay. This package is the single source of truth for the frontmatter shapes and path-allowlist policy validated by the Relay Cloud MCP server and the Relay client utilities.

Zero runtime dependencies. Pure ESM.

Install

npm install @10up/relay-schemas

What's in the box

| Export | Description | | ------------------------------------- | -------------------------------------------------------------------------------- | | notebookSchema | JSON Schema for notebook frontmatter (agenda, status report, retro, etc.) | | prdSchema | JSON Schema for PRD frontmatter (status, domain, epic, version) | | documentWriteSchema | JSON Schema for the Relay Document write-input contract (Claude-authored HTML) | | pathAllowlistSchema | JSON Schema describing the shape of a path-allowlist policy | | defaultPathPolicy | Sensible default policy values (allow/deny globs, size limits, secret patterns) | | DOCUMENT_KINDS | Frozen array of document kinds (status-report, dashboard, allocation, …) | | DOCUMENT_VISIBILITIES | Frozen array of document visibilities (private, shared) | | DOCUMENT_STATUSES | Frozen array of document statuses (draft, published) | | documentSlugPattern | RegExp for the document slug rule (lowercase alphanumeric + hyphens) | | isValidDocumentSlug(slug) | Returns true if slug is 3+ chars and matches the document slug rule | | resolveSchemaForPath(path, policy?) | Returns the schema id (prd.json / notebook.json) for a given path, or null | | isAllowedPath(path, policy?) | Returns true if path is allowed and not denied | | matchGlob(pattern, value) | Minimal glob matcher supporting ?, *, ** |

You can also import individual schema documents:

import notebookSchema from "@10up/relay-schemas/schemas/notebook.json" with { type: "json" }

Quick example

import { notebookSchema, defaultPathPolicy, isAllowedPath } from "@10up/relay-schemas"

// Path policy
isAllowedPath("notebooks/agendas/2026-05-05.md") // → true
isAllowedPath("scripts/ci.sh") // → false (not in allow)
isAllowedPath("anything/.env") // → false (deny wins)

// Validate frontmatter against the notebook schema with your validator of choice.
// AJV example:
import Ajv from "ajv"
import addFormats from "ajv-formats"

const ajv = addFormats(new Ajv({ strict: false }))
const validate = ajv.compile(notebookSchema)

const ok = validate({
  title: "Standup 2026-05-05",
  kind: "agenda",
  created: "2026-05-05T09:30:00Z",
})
console.log(ok, validate.errors)

The schemas use the JSON Schema draft 2020-12 vocabulary. Any compliant validator works (AJV, hyperjump, jsonschema, etc.). This package does not bundle a validator.

Default path policy

defaultPathPolicy ships:

  • allow: requirements/**/*.md, requirements/**/*.prd.md, notebooks/**/*.md, research/**/*.md
  • deny: **/.git/**, **/node_modules/**, **/.env*, **/secrets/**, **/*.key, **/*.pem
  • schema mapping: **/*.prd.mdprd.json, notebooks/**/*.mdnotebook.json
  • limits: maxFileBytes 200 KB, maxBatchBytes 1 MB, maxBatchFiles 20
  • secretPatterns: AWS access keys, Google API keys, OpenAI keys, GitHub tokens, Slack tokens, PEM-format private keys

You can pass your own policy as the second argument to resolveSchemaForPath / isAllowedPath — it must conform to pathAllowlistSchema.

Relay Documents

documentWriteSchema is the canonical input contract for Claude-authored, Fueled-branded HTML documents (status reports, dashboards, allocation reports, QBRs) that Relay Cloud serves directly. These are deliberately separate from the markdown content store and the VitePress build pipeline — the content field carries only the HTML body, and the serving route supplies the brand shell. Documents are upserted by (project, slug).

import { documentWriteSchema, DOCUMENT_KINDS, isValidDocumentSlug } from "@10up/relay-schemas"

DOCUMENT_KINDS // ["status-report", "dashboard", "allocation", "qbr", "generic"]
isValidDocumentSlug("client-status-2026-06-03") // → true
isValidDocumentSlug("Bad Slug") // → false

Because these schemas use the draft 2020-12 vocabulary, compile them with AJV's 2020 entry point: import Ajv from "ajv/dist/2020".

Versioning

Pre-1.0. Expect breaking changes between minor versions until 1.0.0. Schemas evolve as Relay's content model evolves; consumers should pin a known-good version.

License

MIT © 10up Inc.