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/report

v1.2.3

Published

Submission builder for testing-os — turns swarm/run results into the JSON envelope expected by the verifier.

Readme

@dogfood-lab/report

Submission builder for testing-os — turns swarm/run results into the JSON envelope expected by the verifier.

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

Consumer-side packager. Used by source repos to package their dogfood evidence (records, findings) into the JSON envelope that @dogfood-lab/verify will accept on the receiver side. Builds the payload that goes into the repository_dispatch event when a dogfood run completes.

Install

npm install @dogfood-lab/report

Usage

import { buildSubmission } from '@dogfood-lab/report';

const submission = buildSubmission({
  repo: 'org/repo',
  commit: process.env.GITHUB_SHA,
  records: [
    /* dogfood records produced by your swarm/test run */
  ],
  findings: [
    /* findings produced by @dogfood-lab/findings derive */
  ],
});

// submission is now ready for repository_dispatch payload OR direct
// POST to a testing-os ingest endpoint.

What buildSubmission does

  • Validates incoming records and findings against @dogfood-lab/schemas (dogfood-record.schema.json, dogfood-finding.schema.json) before envelope wrapping.
  • Wraps them in the dogfood-record-submission.schema.json envelope.
  • Generates a stable submission_id for correlation across the dispatch → ingest chain.
  • Stamps submitted_at (ISO-8601 UTC).
  • Computes payload-size summary for the size-threshold check on the receiver side.

The caller is responsible for adding GitHub Actions provenance fields (github_run_id, github_workflow_ref) — those get confirmed by @dogfood-lab/verify on the receiver side via the GitHub API. Provenance is the verifier's concern, not the report builder's.

Error shape

buildSubmission throws a structured error when:

  • A record or finding fails local schema validation
  • Required envelope fields are missing (e.g., repo, commit)
  • Embedded payloads exceed the configured size threshold

Each error carries code, message, hint, and cause? per the testing-os structured error contract.

Docs

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

License

MIT © 2026 mcp-tool-shop