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

@huma-protocol/sdk

v0.7.0

Published

Verify Ed25519-signed HUMA score reports offline. Zero-dep except @noble/ed25519. The signer (scanner) and the future HTTP API both emit reports this SDK can verify.

Readme

@huma-protocol/sdk

Verify Ed25519-signed HUMA score reports offline. Zero-dep (except @noble/ed25519).

The HUMA scanner — and the future HTTP API — both emit signed score reports. This SDK lets any downstream consumer verify those reports without trusting the source.

Install

npm install @huma-protocol/sdk
# or
pnpm add @huma-protocol/sdk

Verify a report

import { verifyReport } from '@huma-protocol/sdk';
import type { SignedReport } from '@huma-protocol/sdk';

const signed: SignedReport = JSON.parse(reportJson);
const HUMA_PUBLIC_KEY_B64 = process.env.HUMA_PUBLIC_KEY_B64!;

const ok = await verifyReport(signed, HUMA_PUBLIC_KEY_B64);
if (!ok) throw new Error('signature invalid — report was tampered with');

Optionally bind to a specific key id (defends against rogue signer):

await verifyReport(signed, key, { expectedPublicKeyId: 'huma_pk_prod_2026q2' });

Why

Every score response HUMA emits is signed. Verification is what lets a token foundation, a quest platform, or a DAO take HUMA's number and prove to its own users that the number wasn't edited downstream.

See docs/MOAT.md Layer 0 in the parent repo.

Public surface

verifyReport(signed, publicKeyB64, opts?) // boolean
canonicalize(value) // string — for cross-language verifier implementations
class VerifyError extends Error
interface SignedReport, ScanReport, ScoredWallet, FeatureScores, ...

Not included

This package only verifies. To sign reports, run the HUMA scanner CLI (huma scan) — signing keys live with the operator.

For the API client (/v1/score/{handle} calls) that ships in a later phase, @huma-protocol/sdk will gain a client export. Today it's verify-only because verify is what the wedge needs first.

License

Apache-2.0. Deliberately permissive, and deliberately different from the scanner (@huma-protocol/scanner, BUSL-1.1): this package contains no scoring logic — only signature verification — and it is meant to be embedded wherever a HUMA report needs checking, including in code that competes with us. A verifier nobody is allowed to depend on verifies nothing.