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

docmeta

v1.2.0

Published

Validate the presence and format of document metadata (Markdown frontmatter and more) against JSON Schema. CI-friendly.

Readme

docmeta

Validate the presence and format of document metadata against JSON Schema — built for CI.

docmeta checks the metadata in your documents — Markdown frontmatter and more — against one or more JSON Schemas. It verifies that required fields are present and correctly formatted (a type, an ISO 8601 timestamp, a URI resource); it does not judge prose quality. It ships with the Open Knowledge Format (OKF) schema built in, follows clig.dev conventions, and returns a nonzero exit code (plus optional GitHub annotations) when validation fails.

Install

npm install -g docmeta
# or run it without installing:
npx docmeta validate "**/*.md"

Requires Node.js 24 or later.

Quick start

Point docmeta validate at a file, a directory (walked recursively), or a glob. With no --schema, it validates against the built-in OKF schema.

docmeta validate docs/intro.md
✗ docs/intro.md
    (root)      must have required property 'type'   (line 1)  [google:okf:0.1]
    /timestamp  must match format "date-time"        (line 9)  [google:okf:0.1]

1 file checked, 0 passed, 1 failed, 0 errors

A clean run exits 0; validation failures exit 1; operational errors (no input, unknown schema, parse error) exit 2.

Supported formats

Markdown, MDX, AsciiDoc, reStructuredText, XML, and HTML. Run docmeta schemas to list the built-in schemas and every supported format.

Documentation

Full guides, recipes, and reference live on the documentation site:

https://hawkeyexl.github.io/docmeta/

| Track | What it covers | |-------|----------------| | Get started | Install and run your first validation. | | Set up validation | Stand up validation for a repo: docmeta.config.yaml, per-folder schema overrides. | | Run it in CI | GitHub Actions and other CI recipes, exit codes, and PR annotations. | | Define & evolve schemas | Author a schema, wire up resolution, and version it without breaking the build. | | Reference | Every CLI flag, config key, the schema-resolution precedence chain, and output formats. |

Contributing

Contributions are welcome. See CONTRIBUTING.md for dev setup, the test loop, and how to add support for a new input format.

License

MIT