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

@dogfood-lab/verify

v1.2.3

Published

Central verifier for testing-os. Validates submissions against schema and policy, produces persisted records.

Readme

@dogfood-lab/verify

Central verifier for testing-os. Validates submissions against schema and policy, produces persisted records.

Part of the testing-os monorepo — the operating system for testing in the AI era.

The verifier sits between dispatch and persist: every dogfood submission passes through here before it's written to records/. Returns a structured verdict (ok / rejection_reasons[]) so callers — including the @dogfood-lab/ingest pipeline — can decide whether to persist the record or surface the rejection to the operator.

Install

npm install @dogfood-lab/verify

Usage

import { verify } from '@dogfood-lab/verify';

const result = verify(submission, {
  policy,
  schemas,        // from @dogfood-lab/schemas
  provenance: 'github',
});

if (!result.ok) {
  for (const reason of result.rejection_reasons) {
    console.error(`[${reason.code}] ${reason.message}`);
    if (reason.hint) console.error(`  hint: ${reason.hint}`);
  }
  process.exit(1);
}

// result.record is the persistable artifact

Validators

@dogfood-lab/verify/validators/* ships discrete validators that can be composed or called directly:

| Validator | Purpose | |---|---| | validators/schema.js | JSON Schema check against @dogfood-lab/schemas | | validators/policy.js | Per-repo policy compliance (prototype-pollution-safe deep merge) | | validators/provenance.js | GitHub Actions run-ID confirmation via API (with timeout guard) | | validators/steps.js | Step-by-step contract checks (gate accumulation, ordering) | | validators/verdict.js | Final verdict synthesis from upstream validator results |

Import a single validator:

import { validateSchema } from '@dogfood-lab/verify/validators/schema.js';
import { validateProvenance } from '@dogfood-lab/verify/validators/provenance.js';

Submission envelope

The full envelope shape is defined by @dogfood-lab/schemas (dogfood-record-submission.schema.json). Minimum required fields:

{
  "repo": "org/repo",
  "commit": "<git-sha>",
  "submitted_at": "2026-05-14T15:00:00Z",
  "records": [/* one or more dogfood-record envelopes */]
}

Provenance fields (github_run_id, github_workflow_ref) are required when provenance: 'github' is set. The verifier confirms the run ID against the GitHub Actions API before accepting.

Error shape

Each rejection_reasons[] entry follows the testing-os structured error shape:

{
  code: 'POLICY_GATE_FAILED' | 'SCHEMA_MISMATCH' | 'PROVENANCE_UNVERIFIED' | ...,
  message: string,
  path: string,        // JSON path to the offending field
  hint?: string,       // operator-facing remediation hint
}

Docs

📖 Full handbook: https://dogfood-lab.github.io/testing-os/handbook/

License

MIT © 2026 mcp-tool-shop