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

@neutils/og-check

v0.9.5

Published

Fetch a URL and render its OpenGraph / Twitter Card metadata.

Readme

og-check

Fetch a URL and render its OpenGraph / Twitter Card metadata, and validate that the required fields are present.

og-check screenshot

Usage

og-check [OPTIONS] <url>

Arguments

| Argument | Description | |----------|-------------| | url | URL to fetch and inspect |

Options

| Option | Short | Description | |--------|-------|-------------| | --output-format | -o | Preview format (opengraph, twitter, table, json, none) | | --issue-format | -f | Validation issue format (human, json, ci) |

Output streams

og-check writes two independent streams:

  • stdout — the "success story": a preview of the page's metadata, shaped by --output-format.
  • stderr — the "failure story": validation issues, shaped by --issue-format.

As a convenience for pipelines, --issue-format json is emitted on stdout when --output-format none (i.e. when nothing else would be written to stdout). This lets | jq … work on the issue report without shell redirection.

The process exits with status 1 if any errors were reported; warnings alone do not fail the run.

Preview formats (--output-format)

| Value | Description | |-------|-------------| | opengraph | Styled preview of og:* fields (default in a terminal) | | twitter | Styled preview of twitter:* fields, falling back to og:* | | table | All meta tags as a markdown table, grouped by namespace | | json | All meta tags as a JSON document, grouped by namespace | | none | Skip the preview entirely (default under CI) |

The chosen format also selects which schema(s) are validated:

  • opengraph → validates OpenGraph required fields (og:title, og:image, og:type, og:url)
  • twitter → validates Twitter Card required fields (twitter:card, and a title/image from either namespace)
  • table, json, none → validates both schemas

Issue formats (--issue-format)

| Value | Description | |-------|-------------| | human | Markdown with ✅ / ❌ / ⚠️ glyphs, grouped by schema (default in a terminal) | | ci | GitHub / Forgejo Actions workflow commands (::error title=…::…) — default under CI | | json | Linter-style JSON document with tool, version, status, summary, issues[] |

CI auto-detection

When the GITHUB_ACTIONS or FORGEJO_ACTIONS environment variable is set, og-check defaults to:

  • --output-format none — no preview noise in the job log
  • --issue-format ci — annotations surface inline on the PR

Either default can be overridden by passing the flag explicitly.

Note: Inline images (og:image, twitter:image) are only displayed when your terminal supports the Kitty graphics protocol. In other terminals, only the image URL is shown.

Examples

# Default: rendered OpenGraph preview, human-readable issues
og-check https://github.com/deevus/neutils

# Twitter Card preview (falls back to og:* fields when twitter:* are absent)
og-check -o twitter https://github.com/deevus/neutils

# All meta tags as a table, grouped by namespace
og-check -o table https://github.com/deevus/neutils

# Machine-readable preview
og-check -o json https://github.com/deevus/neutils

# CI mode: no preview, workflow-command annotations on stderr
og-check -o none -f ci https://github.com/deevus/neutils

# Structured JSON issue report (suitable for piping into jq)
og-check -o none -f json https://github.com/deevus/neutils