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

@ternent/concord-protocol

v0.0.12

Published

TypeScript implementation of the Concord protocol core: entries, commits, and ledger containers with canonical hashing rules.

Readme

Concord Protocol Package

TypeScript implementation of the Concord protocol core: entries, commits, and ledger containers with canonical hashing rules.

Overview

This package provides:

  • Canonical data structures for Concord ledgers
  • Deterministic hashing for EntryID and CommitID
  • Canonical signing payloads and bytes
  • Genesis commit creation
  • Commit chain traversal, replay helpers, and validation

Pending entries and application state are intentionally out of scope. User management, access control, encryption policy, and networking are out of scope.

Installation

npm install @ternent/concord-protocol

Quick Start

import {
  createLedger,
  deriveEntryId,
  deriveCommitId,
  getCommitChain,
  getEntrySigningPayload,
} from "@ternent/concord-protocol";

const ledger = await createLedger({ implementation: "concord-js" });

const entry = {
  kind: "concord/user/added",
  timestamp: "2026-01-01T00:00:00Z",
  author: "author-1",
  payload: { id: "user-1" },
  signature: null,
};

const entryId = await deriveEntryId(entry);
const signingPayload = getEntrySigningPayload(entry);

const chain = getCommitChain(ledger);
console.log(entryId, signingPayload, chain);

API Notes

  • EntryID excludes the signature field
  • CommitID hashes the full commit structure
  • Genesis commits are not replayed and contain no entries
  • Canonical JSON uses lexicographic key ordering with no whitespace
  • Inputs must be plain JSON values (no toJSON, no non-finite numbers)
  • Hashing is SHA-256 over UTF-8 bytes with lowercase hex output

Tests

pnpm --filter @ternent/concord-protocol test

Shared vectors live in packages/concord-test-vectors.