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

@supawatch/target-pgtap

v0.14.2

Published

A plan-counted pgTAP structural test suite generated from live Postgres by supawatch, RLS and policy assertions included.

Readme

@supawatch/target-pgtap

The pgTAP target for supawatch. Emits structure.pgtap.sql: a plan-counted structural test suite asserting what your schema actually is. Per table: has_table, has_column, null and not-null constraints, primary key and foreign key columns. Tables with row level security enabled also get tests.rls_enabled and policies_are with the exact policy names.

targets: [{ kind: "pgtap" }]

Run it with pg_prove or supabase test db against a database with the pgtap extension installed. The plan(N) count is derived from the emitted assertions, so a truncated file fails loudly instead of passing quietly; the repo's suite locks that arithmetic.

Emission is tested against real introspected schemas. Executing the suite needs pgtap in your database, which is on you.

MIT.