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

@mrtdown/ingest-contracts

v2.0.0-alpha.27

Published

Shared ingest payload schemas for MRTDown evidence ingestion

Downloads

902

Readme

@mrtdown/ingest-contracts

Shared Zod schemas and TypeScript types for MRTDown ingest webhook payloads.

This package is intentionally small so external evidence producers can validate payloads without depending on @mrtdown/triage or its LLM/runtime implementation dependencies.

import {
  IngestPayloadSchema,
  type IngestPayload,
} from '@mrtdown/ingest-contracts';

const payload: IngestPayload = IngestPayloadSchema.parse({
  content: [
    {
      source: 'news-website',
      title: 'Example disruption report',
      summary: 'Trains are delayed due to a track fault.',
      url: 'https://example.com/report',
      createdAt: '2026-05-23T09:00:00+08:00',
      articleText:
        'The operator said commuters should expect an additional 20 minutes of travel time.',
      articleTextSource: 'publisher',
      articleTextFetchedAt: '2026-05-23T09:01:00.000Z',
    },
  ],
});

News Articles

News website payloads may include optional article enrichment fields from crawler-side extraction:

  • articleText is extracted article body text, or a compact metadata fallback.
  • articleTextSource is publisher, archive, or metadata.
  • articleTextFetchedAt is when the article text was fetched or derived.

Crowd Reports

Accepted and moderated public commuter reports use the crowd-report content source. These payloads are intended for reports that are already safe to become canonical evidence.

const payload: IngestPayload = IngestPayloadSchema.parse({
  content: [
    {
      source: 'crowd-report',
      reportId: 'accepted-20260523-0903-btl-001',
      text: 'Several commuters report 15 minute delays on the BTL.',
      createdAt: '2026-05-23T09:04:00+08:00',
      observedAt: '2026-05-23T09:03:00+08:00',
      lineIds: ['BTL'],
      stationIds: ['BCL'],
      directionText: 'towards Expo',
      effect: 'delay',
      delayMinutes: 15,
      reportCount: 4,
      url: 'https://example.com/crowd-reports/accepted-20260523-0903-btl-001',
    },
  ],
});

IngestContentCrowdReportEffectSchema, IngestContentCrowdReportEffects, and IngestContentCrowdReportSource are exported for producers that need to share the crowd-report source and effect values.

Contract rules:

  • reportId must be stable and non-PII.
  • createdAt is when the producer accepted the report or cluster for dispatch.
  • observedAt is when the condition was observed.
  • text is the natural-language evidence passed to triage.
  • At least one lineIds or stationIds entry is required.
  • url is required because canonical evidence stores a public sourceUrl.
  • Site-local metadata is rejected. Keep submitter identities, IP addresses, user-agent strings, contact fields, moderation notes, abuse scores, and challenge tokens out of this payload.