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

@spectastic/schema

v0.1.0-pre.28

Published

Spec-html validation schema and engine. The TypeScript module form of the spec-* vocabulary's grammar — used by @spectastic/cli, MCP servers, and editor extensions.

Downloads

80

Readme

@spectastic/schema

npm downloads node license

The TypeScript module form of the spec-html vocabulary's grammar. A library consumers — @spectastic/cli, the future VS Code extension, the MCP server, the kernel — import to judge spec validity against the same rules.

Install

npm i @spectastic/schema
# or pnpm add @spectastic/schema
# or yarn add @spectastic/schema

Use

import { validate, validateMany, rules, type Finding } from '@spectastic/schema';

// Single file
const findings: Finding[] = validate(htmlString, { file: 'specs/001/spec.html' });

// Multi-file (cross-file rules see the whole set)
const all = validateMany([
  { html: html1, file: 'a.html' },
  { html: html2, file: 'b.html' },
]);

// Walk the registry
for (const rule of rules) {
  console.log(rule.id, rule.scope, rule.defaultSeverity, rule.description);
}

Surface

| Export | Kind | Purpose | | ------------- | ------------- | ------------------------------------------------------------------------- | | validate | function | Validate one HTML string. Runs all per-file rules plus cross-file over [doc]. | | validateMany| function | Validate many HTML strings together. Cross-file rules see all docs. | | rules | readonly array| The canonical rule registry. | | Finding | type | One violation. Fields: file, line, column, rule, severity, message, fixHint?, relatedLocations?. | | Rule | type | Union of PerFileRule | CrossFileRule. | | PerFileRule | type | Inspects one document. | | CrossFileRule | type | Inspects the whole set. | | Severity | type | "error" | "warning". | | Location | type | { file, line, column }. | | ValidateOptions | type | { file? }. | | ParsedDocument | type | { html, file, ast, status? }. |

Rules

Thirty-four rules, grouped by what they protect. rules is the canonical registry — enumerate it rather than trusting a list in a README to stay current.

Artifact shape — requirement-id-required, task-id-required, task-title-bold-scope, empty-document, date-format, id-within-file-unique, file-too-large.

Change proposals — delta-op-required, delta-target-required, data-delta-shape, risk-target-required, risk-status-required.

Scope and sizing — no-missing-defer-to, no-broken-defer-to, invest-row-failed, rice-well-formed, split-well-formed, format-band-coupling, matrix-winner-integrity.

Open questions — no-unresolved-question, no-placeholder-question.

Cross-file integrity — no-duplicate-ids, spec-id-unique, spec-parent-well-formed, parent-child-reciprocity, verify-view-missing, verify-view-stale.

Contracts and objectives — contract-declaration-shape, contract-name-unique, slo-target-required, slo-well-formed.

Grounding and security — corpus-citation-form, no-executable-content, hidden-instruction-pattern.

Severity for the status-dependent rules downgrades on a draft or review artifact and skips where status is unset — an unfinished document is not a broken one.

Provenance

Implements spec 002-validate-cli. See specs/002-validate-cli/spec.html in the repo for the contract; design.html for the decisions (parse5, in-house SARIF, TS-module schema); tasks.html for the breakdown.