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

@dointhai/owlwarden-sdk

v1.1.0

Published

Types and zod schemas for owlwarden reports, rules, and coverage. Install `owlwarden` to run the scanner.

Readme

@dointhai/owlwarden-sdk

Types and zod schemas for owlwarden output. Install this if you consume owlwarden's JSON — a dashboard, a bot, a CI gate of your own — rather than just running the CLI.

npm i @dointhai/owlwarden-sdk
import { reportSchema, type Report } from "@dointhai/owlwarden-sdk";

const report: Report = reportSchema.parse(JSON.parse(stdout));

for (const finding of report.findings) {
  console.log(finding.id, finding.severity, finding.location.path);
}

The schemas are not a hand-written description of the engine's output. A test in the repository serialises a report from the Rust engine and parses it with these schemas, so the two cannot drift: if the engine changes a field and this package does not, the build fails. See ADR 0010.

What is worth reading before you branch on it

  • suppressedCount exists so that findings: [] is never mistaken for "no problems". Zero findings with a non-zero suppressed count means someone made a judgement call you may want to look at.
  • confidence is confirmed, likely, or possible. Static analysis cannot produce confirmed; only correlation with a live probe can. Treat possible as "worth a human's attention", not "broken".
  • truncated means limits were hit and the report is incomplete. A truncated report always fails the CI gate (shouldFail / --ci exit 1).
  • Rule ids are permanent. Safe to hard-code, reference in config, and store.

Licence

MIT OR Apache-2.0.