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

@titan-design/review-schema

v0.1.0

Published

Zod schemas for titan-review rounds (titan-review/round@2) and their feedback (titan-review/feedback@1)

Readme

@titan-design/review-schema

The zod schemas for titan-review rounds and the feedback a round returns. The package is zod-only: zod (v4) is its one peer dependency and it has no runtime dependencies of its own. @titan-design/review-harness serves rounds against these schemas; anything else that writes or reads a round imports them from here instead of copying them.

Schema ids

| Constant | Value | Meaning | | --------------------------- | ------------------------- | --------------------------------------------------------------------- | | MANIFEST_SCHEMA_ID | titan-review/round@2 | The round contract. RoundSchema accepts only this id. | | LEGACY_MANIFEST_SCHEMA_ID | titan-review/round@1 | A round written before the contract. ManifestSchema still reads it. | | FEEDBACK_SCHEMA_ID | titan-review/feedback@1 | The submission a round returns, validated by FeedbackSchema. |

Exports

  • RoundSchema: the round@2 contract (sections with deciding, changed and context, a strip kind on each section with frames, signsOff on each pick-one, a loopback storybookUrl).
  • ManifestSchema: any round the review page can render, round@1 included.
  • FeedbackSchema, RecommendationSchema, and the section, variant, question and contrast schemas they compose.
  • SHIP_OPTIONS, the only options a merge-bound question may offer.
  • isLoopbackUrl(url), true only for an http(s) URL on 127.0.0.1, localhost or [::1].
  • manifestJsonSchema() and feedbackJsonSchema(), the JSON Schema an author writes against.
  • The inferred types: ManifestInput, Manifest, Feedback, Recommendation, Question, Section, Variant and the rest.
import { RoundSchema, MANIFEST_SCHEMA_ID, type ManifestInput } from '@titan-design/review-schema'

const round: ManifestInput = { schema: MANIFEST_SCHEMA_ID /* ... */ }
const result = RoundSchema.safeParse(round)

JSON Schema files

schema/round.schema.json and schema/feedback.schema.json ship with the package (import them as @titan-design/review-schema/schema/round.schema.json). They are generated from src/schema.ts by pnpm --filter @titan-design/review-schema schema, and a test fails if they drift.