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

@glyphp/conformance

v1.0.3

Published

Conformance suite — validate any Glyph server against the protocol spec

Downloads

779

Readme

@glyphp/conformance

An executable conformance suite for the Glyph Protocol. Point it at any Glyph server and it reports whether the server matches the spec.

CLI

glyph-conformance http://localhost:3100

Exit code 0 if every check passes, 1 otherwise.

Library

import { runConformance, formatReport } from '@glyphp/conformance'

const report = await runConformance('http://localhost:3100')
console.log(formatReport(report))
console.log(report.passed) // boolean

Pass an in-process handler instead of hitting the network — useful in tests:

import { GlyphServer } from '@glyphp/server'

const server = new GlyphServer()
const report = await runConformance('http://glyph', { fetch: server.fetch })

What it checks

The suite is non-destructive — it exercises discovery and error handling only, and never calls a glyph (which would require knowing valid inputs):

  • /health reports a protocol version
  • the handshake accepts the supported protocol version and returns a valid HandshakeResponse
  • the handshake rejects a version mismatch with 426
  • /lexicon returns valid LexiconEntry objects
  • a glyph card validates against the schema
  • a glyph card's signature and content hash verify
  • an unknown glyph returns 404 NOT_FOUND in the GlyphError envelope
  • the bundled Sanitization schema validates representative samples

Response shapes are validated against the JSON Schemas bundled from spec/schemas/.

What it does not check

Because the suite never calls a glyph, it never sees a SealedEnvelope or an inspection report produced by a live call. The schema.sanitization check confirms only that the Sanitization wire schema is published and self-consistent — it does not prove that a server actually sanitizes its output. Verifying inert-data behavior end to end requires invoking a glyph with known-hostile input, which is destructive and therefore out of scope here; 04-inert-data demonstrates it instead.