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

@a5c-ai/sdk

v1.1.1

Published

TypeScript/Node.js SDK for reading and writing `a5cforge/v1` collaboration data stored in a Git repo under `.collab/**`.

Readme

@a5c-ai/sdk

TypeScript/Node.js SDK for reading and writing a5cforge/v1 collaboration data stored in a Git repo under .collab/**.

Install

npm i @a5c-ai/sdk

Concepts

  • Collab events live in the repository under .collab/** as JSON/NDJSON/Markdown event files.
  • Snapshot is a view of collab events at a Git revision (a treeish) plus optional inbox refs.
  • Inbox refs (recommended for writes) are Git refs like refs/a5c/inbox/<name> that hold an append-only .collab/** tree. They let you stage collaboration changes without touching the currently checked-out branch.

Read data (snapshot + renderers)

import { openRepo, loadSnapshot, listIssues, renderIssue } from "@a5c-ai/sdk";

const repo = await openRepo(process.cwd());
const snap = await loadSnapshot({
  git: repo.git,
  treeish: "HEAD",
  inboxRefs: ["refs/a5c/inbox/ui"],
});

for (const id of listIssues(snap)) {
  const issue = renderIssue(snap, id);
  console.log(issue?.issueId, issue?.title);
}

Common helpers:

  • listIssues(snapshot), renderIssue(snapshot, issueId)
  • listPRs(snapshot), renderPR(snapshot, prKey)

Write events

The SDK provides file-writers that emit a5cforge/v1 event files under .collab/**. You are responsible for committing them (or writing them into an inbox ref via your own Git plumbing).

import { openRepo, HlcClock, loadHlcState, saveHlcState, writeIssueCreated } from "@a5c-ai/sdk";

const actor = "alice";
const repo = await openRepo(process.cwd());
const clock = new HlcClock(await loadHlcState(actor));

const wr = await writeIssueCreated(
  { repoRoot: repo.root, actor, clock },
  { issueId: "issue-123", title: "Hello", time: new Date().toISOString() }
);

await saveHlcState(actor, clock.now());
console.log("wrote", wr.path);

See exports from @a5c-ai/sdk:

  • writeIssueCreated, writeCommentCreated, writePrRequest, writePrProposal, writeAgentClaimChanged, …
  • stageFiles(repoRoot, [path]) to git add the created paths

Treeish vs inbox refs

  • treeish is any Git revision you can git rev-parse (e.g. HEAD, main, a commit SHA). It defines the “base” collab history.
  • inboxRefs are additional refs whose .collab/** events are merged into the snapshot (useful for “incoming” PRs/issues, UI inboxes, etc.).

In many apps you can keep treeish: "HEAD" and rely on inboxRefs for all writes.

License

See repository license.