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

@nostrwatch/schemata

v0.0.1

Published

``` Note: This package will be migrated to nostrability/schemata once all events that @nostrwatch tests have a schema specified. ```

Readme

Note: This package will be migrated to nostrability/schemata once all events that @nostrwatch tests have a schema specified.

@nostrwatch/schemata

A template for simplifying the validation of nostr events, their attributes and their respective tags using JSON-Schema standards.

Related

Usage

  1. Download ZIP file (all languages) or include package (js only for now)
  2. Validate .json schemas against nostr events.

Use in your own pipline

You shouldn't. You should write a wrapper or use one that already exists. Wrappers must use the following typings.

type NSchemaResult [ boolean, NSchemaMessage[] ]
interface NSchemaMessage {
    level: "info" | "warning" | "error" 
    message: string
} 

And provide the following interface:

validate(event: NostrEvent): NSchemaResult
validateMany(events: NostrEvent[]): NSchemaResult[]

Contribute

Setup

  1. Fork the repo.
  2. npm/yarn/pnpm install
  3. npm/yarn/pnpm build
  4. npm/yarn/pnpm test

Writing Schemas

Familiarize yourself with the aliases section and the file structure.

  1. Create a new directory for your NIP, and a directory for each kind. ...this is going to be annoying to write, so it should probbaly be automated.

FS Conventions

This toolkit uses path conventions for build and testing schemata.

nips/nip-XY/kind-N/schema.yaml

Kinds are assumed to belong to a NIP, but if you are working with an experimental kind, you won't have a NIP. For these situations, simply place the kind into a nipless "nipless"

nips/nipless/kind-X