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

@git-stunts/git-warp

v17.0.0

Published

Deterministic WARP graph over Git: graph-native storage, traversal, and tooling.

Readme

CI License npm version

git-warp commits truth, folds truth, and reveals truth under law.

It stores causal graph history in Git objects and refs. Writes are admitted through patches. Reads happen through worldlines, strands, and observers. Provenance, replay, and explicit historical coordinates are part of the model, not bolted-on afterthoughts.

Quick start

import { openWarpGraph } from '@git-stunts/git-warp';
import GitPlumbing from '@git-stunts/plumbing';
import { GitGraphAdapter } from '@git-stunts/git-warp';

const plumbing = new GitPlumbing({ cwd: '.' });
const persistence = new GitGraphAdapter({ plumbing });

const graph = await openWarpGraph({
  persistence,
  graphName: 'events',
  writerId: 'agent-1',
});

// Commit: admit a claim into shared causal reality
const patch = await graph.patches.createPatch();
patch.addNode('user:alice').setProperty('user:alice', 'role', 'admin');
await patch.commit();

// Reveal: read the admitted truth through a live worldline
const worldline = graph.query.worldline();
const props = await worldline.getNodeProps('user:alice');

What git-warp is

git-warp is a Git-native implementation of WARP: Worldline Algebra for Recursive Provenance.

  • Offline-first — writers work independently, converge later
  • Multi-writer — each writer owns its own ref, no coordination
  • Append-only — history is never rewritten
  • Deterministic — same patches, any order, same materialized state
  • Provenance-complete — every value traces to exactly one producing patch
  • Speculative — strands are causal lanes for counterfactual work
  • Observable — worldlines, observers, and apertures shape what you see

The admission architecture

openWarpGraph() returns a frozen capability bag organized around three architectural moments:

| Moment | Capabilities | What it does | |--------|-------------|--------------| | Commitment | patches, strands, comparison | Admits claims into frontier-relative truth | | Folding | checkpoint | Re-expresses admitted history as operational artifacts | | Revelation | query, subscriptions, provenance | Exposes admitted truth under bounded rights | | Governance | sync | Transports and admits remote suffixes |

Core nouns

| Term | Meaning | |------|---------| | Worldline | Canonical admitted causal lane. The shared truth others may rely on. | | Strand | Speculative causal lane with fork provenance. Private until admitted. | | Braid | Plural composition over a family of lanes. Not itself a lane. | | Observer | Filtered read-only projection through an aperture. | | Aperture | The boundary that shapes what an observer can see. | | Patch | A claim: a set of operations over a bounded causal site. | | Receipt | Provenance-bearing witness of an admission outcome. |

Why Git

Git and WARP fit together because both are:

  • append-only in spirit
  • content-addressed
  • distributed and multi-writer
  • history-preserving

Each writer appends patch commits under refs/warp/<graph>/writers/<writerId>. Commits point at Git's empty tree — graph history stays orthogonal to your source tree. Sync happens through normal git push / git fetch.

When to use it

| Use case | Fit | |----------|-----| | Offline-first multi-writer convergence | Strong | | Agent/tool substrate with causal history | Strong | | Graph semantics without inventing merge law | Strong | | Speculative lanes for what-if exploration | Strong | | High-throughput real-time execution | Use Echo instead | | General-purpose OLTP | Use Postgres | | Full-text search / analytics | Use purpose-built engines | | Time-travel debugging UI | Use warp-ttd on top of git-warp |

Documentation

Substrate stack

git-warp is part of the @git-stunts substrate:

| Package | Role | |---------|------| | @git-stunts/plumbing | Git operations | | @git-stunts/git-cas | Content-addressable storage with dedup | | @git-stunts/alfred | Resilience (retry, timeout, circuit breaker) | | @git-stunts/trailer-codec | Commit message trailers | | @git-stunts/vault | Secrets management via OS keychain |

License

Apache-2.0