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

@napplet/conformance

v0.16.2

Published

Framework-agnostic napplet protocol conformance engine — reference mock shell, per-NAP envelope validators, manifest validator, check registry, and reporters

Downloads

1,826

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

sandwichessandwiches

Keywords

nostrnappletconformanceprotocolnip-5dtesting

Readme

@napplet/conformance

Framework-agnostic conformance engine for the napplet protocol. It lets a napplet self-verify that it conforms to NIP-5D + the NAP wire protocol before publishing, in two scopes that share this one engine:

  • Headless / CI — driven by the napplet-conformance Playwright CLI.
  • Standalone web runtime — the single-window apps/conformance app.

v1 is zero-config protocol conformance: NIP-5D manifest-event validity, boots under sandbox="allow-scripts", receives runtime-injected window.napplet, every emitted postMessage envelope validates against the per-NAP validators, graceful degradation when domains are absent, and no forbidden globals.

What's in the box

  • validateEnvelope(msg) — runtime validation of any domain.action envelope a napplet emits, across all active NAP domains. Catches malformed payloads, unknown types, and napplets that put shell→napplet (inbound) traffic on the wire.
  • validateManifestEvent(event) — checks that a resolved Nostr event is a NIP-5D napplet manifest (5129, 15129, or 35129) with a hashed /index.html path and bare known requires domains.
  • validateManifest(html) — compatibility wrapper for older HTML-only harnesses. HTML alone cannot prove a signed NIP-5D manifest event.

The validator surface is kept in lockstep with @napplet/nap by a drift test, so a new NAP message type cannot ship without matching conformance coverage.

For intent envelopes, conformance checks the merged intent.invoke request/result carrier. Requests require an archetype, optional action and convention remain orthogonal, and results expose canonical handling state. Convention strings and payloads remain opaque local choices.

This non-normative description follows the living NAP-INC and NAP-INTENT documents.

import { validateEnvelope, validateManifestEvent } from '@napplet/conformance';

validateEnvelope({ type: 'relay.subscribe', id: 'a', subId: 'b', filters: [{ kinds: [1] }] }).ok; // true
validateManifestEvent(resolvedManifestEvent).ok; // true when the NIP-5D event is well-formed

This package is a development/testing tool. It is not loaded inside the napplet sandbox at runtime.

Install

pnpm add -D @napplet/conformance

JSR consumers can import the same source package:

import { runConformance, validateEnvelope, validateManifest } from 'jsr:@napplet/conformance';

Most application projects should use the napplet-conformance CLI wrapper in CI. Use this package directly when you are embedding the engine in a custom harness, building a shell-side test runtime, or validating individual envelopes and resolved manifest events in unit tests.

Common Workflows

Validate one envelope

import { validateEnvelope } from '@napplet/conformance';

const verdict = validateEnvelope({
  type: 'storage.get',
  id: 'request-1',
  key: 'settings',
});

if (!verdict.ok) {
  console.error(verdict.errors);
}

Validate a resolved manifest event

import { validateManifestEvent } from '@napplet/conformance';

const verdict = validateManifestEvent(resolvedManifestEvent);

if (!verdict.ok) {
  throw new Error(verdict.errors.map((e) => e.message).join('\n'));
}

Run the full engine

import { makeContext, runConformance } from '@napplet/conformance';

const context = makeContext({
  manifestHtml: '<!doctype html><html><head></head><body></body></html>',
});
const run = runConformance(context);

for (const check of run.checks) {
  console.log(check.id, check.status);
}

Public Surface

  • Envelope validation: validateEnvelope, knownEnvelopeTypes, ENVELOPE_SPECS
  • Manifest validation: validateManifestEvent, validateManifest
  • Reference shell harness: createReferenceShell, attachReferenceShell
  • Browser boot collection: bootAndCollect
  • Context helpers: makeContext, buildContext
  • Runner and report helpers: runConformance, toJson, toPretty, toJUnit

CLI Pairing

The package intentionally stays framework-agnostic. For a project-level command that launches real Chromium against a built napplet, use the companion napplet-conformance CLI shipped from @napplet/conformance-cli.