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

@kerits/core

v0.3.4

Published

Pure functional core for KERI: CESR encoding, SAID computation, KEL/TEL/ACDC operations, validation, signing primitives, canonical data, and threshold logic. No I/O, no storage, no side effects — runs in any JavaScript runtime (browser, Node.js, Bun, Clou

Downloads

206

Readme

@kerits/core

Pure functional core for KERI: CESR encoding, SAID computation, KEL/TEL/ACDC operations, validation, signing primitives, canonical data, and threshold logic. No I/O, no storage, no side effects — runs in any JavaScript runtime (browser, Node.js, Bun, Cloudflare Workers).

Install

bun add @kerits/core

Quick Start

import {
  KELEvents,
  generateKeyPair,
  encodeKey,
  nextKeyDigestQb64FromPublicKeyQb64,
} from '@kerits/core';

// Generate current and next Ed25519 key pairs
const current = generateKeyPair();
const next = generateKeyPair();

// Encode public keys to CESR qb64
const currentKeyQb64 = encodeKey(current.publicKey).qb64;
const nextKeyQb64 = encodeKey(next.publicKey).qb64;

// Compute the next-key digest commitment
const nextKeyDigest = nextKeyDigestQb64FromPublicKeyQb64(nextKeyQb64);

// Build and finalize an inception event
const { unsignedEvent } = KELEvents.buildIcp({
  keys: [currentKeyQb64],
  nextKeyDigests: [nextKeyDigest],
});
const { event, said } = KELEvents.computeSaid(unsignedEvent, true);

console.log('AID:', said);

Features

  • CESR encoding/decoding — keys, signatures, digests, and CESR attachment groups
  • SAID computation — keripy-compliant insertion-order derivation with deriveSaid / recomputeSaid and typed DerivationSurface descriptors
  • KEL event building — inception, rotation, interaction, delegation events with version-string convergence
  • TEL event types — registry inception/rotation, credential issuance/revocation
  • KEL validation — chain validation, SAID verification, threshold checking, key commitment verification
  • Ed25519 signing — key generation, signing, verification with CESR encoding
  • Branded typesAID, SAID, PublicKey, Signature for compile-time safety

Documentation

Full API documentation and guides: kerits.dev

Try kerits interactively: kerits.id

KERIpy Compliance

SAID computation and CESR encoding are cross-validated against the KERIpy reference implementation using shared neutral fixtures and Python-generated expected values. See the compliance testing guide for details.

Building

# Run tests and build docs (from repo root):
make test-core

# Or from the package directory:
make -C packages/core test

License

Apache License 2.0 — see LICENSE.