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

mentu-pdv

v1.0.0

Published

Frontmatter validation for evidence-disciplined corpora: the PD-1 schema (derivability-tested fields, measured summary ban), demotion sets, read-back meter. Read-only by construction.

Readme

pdv — frontmatter validation for evidence-disciplined corpora

pdv validates the PD-1 frontmatter schema over a markdown corpus: an S1-passing field set (id, status, supersession links, governance fields, lang, aliases, links, class), staleness horizons, and a ban on authored summary/description fields on document-class files — a ban with a measurement behind it: used as a sole locator, a one-line summary layer routed agents to the right document on 52.0% of questions against plain search's 80.4% (doi:10.5281/zenodo.21960138).

It is read-only by construction: it reports, emits a demotion set for a consuming locator (see mentu-navigator), and registers promotions in a read-back meter — it never edits a corpus.

Install & use

npm install -g mentu-pdv

pdv check .                        # validate; exit 1 on actionable errors
pdv check . --json                 # machine-readable report
pdv demotions . > demotions.json   # the artifact a locator consumes
pdv promote docs/x.md --commitment=<id>   # register a promoted artifact in the read-back meter

Per-corpus conventions (status vocabulary, class globs, immutable paths, ignore globs) live in a config file kept outside the corpus — see pdv.config.example.yaml — and are passed with --config.

Design rules

  • Fields present are validated; fields absent are counted (adoption is measured, not mandated).
  • Staleness demotes ranking, never excludes.
  • Findings inside declared immutable paths are report-only.
  • Determinism: same tree + same --as-of ⇒ byte-identical output.
  • A corpus is one repository; nested repos validate separately.

Evidence discipline

Every behavioral default in this tool traces to a registered study in a public evidence program: the summary ban to doi:10.5281/zenodo.21960138, the demote-never-exclude and read-back-meter semantics to the same program's memory-promotion result (files promoted to a durable memory directory were later read in 2 of 157 eligible cases). Claims not backed by a registered result are design stances, labeled as such in the spec.

License: Apache-2.0.