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

@gravitylock/gwt-verify

v1.1.1

Published

Offline verifier for Gravity Lock signed artifacts

Readme

gwt-verify

Offline verifier CLI for Gravity Lock signed artifacts.

Quick start

cd verifier
npm install
npm test

Commands

  • gwt-verify <artifact.json>
  • gwt-verify <artifact.json> --json
  • gwt-verify <artifact.json> --pubkey <fingerprint>
  • gwt-verify <artifact.json> --bundle <bundle.json> (custody cross-check)
  • gwt-verify <artifact.json> --sample <n> (pipeline trace replay sample size)
  • gwt-verify --version

Example usage

# Verify extension signed bundle
gwt-verify ./examples/bundle.json

# Machine-readable output
gwt-verify ./examples/bundle.json --json

# Enforce expected signer fingerprint
gwt-verify ./examples/bundle.json --pubkey "aa:bb:cc:..."

# Verify custody manifest against referenced bundle
gwt-verify ./examples/custody.json --bundle ./examples/bundle.json

# Verify pipeline trace with bounded replay sample size
gwt-verify ./examples/pipeline_trace.json --sample 25

Packaging smoke

  • npm test runs verifier unit/integration tests
  • npm run test:pack builds a tarball and verifies install-path execution (gwt-verify --version)

Exit codes

  • 0: all checks pass
  • 1: signature verification failed
  • 2: canonical hash mismatch
  • 3: semantic verification failure
  • 4: unknown schema or unsupported artifact type
  • 5: --pubkey fingerprint mismatch
  • 99: malformed input / read error / bad flags

Current coverage

  • Extension signed bundles (gwt.bundle.v1) with:
    • canonical hash re-derivation
    • Ed25519 signature verification
    • audit prev_event_hash chain check
    • schema dispatch for 0.12 / 0.14 / 0.15 / 0.16
  • Additional artifact semantics:
    • gwt.custody_manifest.v1: referenced bundle hash cross-check (--bundle)
    • gwt.pipeline_trace.v1: reconstruction replay against transformed_input_hash
    • gwt.coherence_report.v1: recompute and validate summary statistics
    • gwt.nucleus.v1: recompute weighted composite nucleus score
    • gwt.unified_bundle.v1: container signature + embedded extension/server bundle verification

Publish and npx flow

Use:

  • verifier/RELEASE.md for full release runbook (version bump, pack/install smoke, publish, post-publish npx validation)
  • verifier/PUBLISH_READY_CHECKLIST.md for operator checklist
  • npm run release:check (or npm run release:check:full) for executable readiness checks