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

@jiplabs/versioning

v0.1.1

Published

Generic port-based append-only event journal with durable sequencing.

Downloads

69

Readme

@jiplabs/versioning

Generic, port-based append-only event journal with durable monotonic sequencing.

Status: V0.1.x frozen contract · License: MIT

This library is product-agnostic. JipComply is one consumer that wires PostgreSQL via adapters; the package itself has no @jipcomply/* runtime dependencies.

Non-goals

  • Full event sourcing / replay
  • State reconstruction at time T
  • Payload schema upcasting
  • Distributed transaction atomicity
  • Built-in database adapters

Install

npm install @jiplabs/versioning

Minimal usage

import {
  appendEvent,
  listEvents,
  type VersioningPorts,
} from "@jiplabs/versioning";

declare const ports: VersioningPorts;

await appendEvent(ports, {
  entityId: "entity-1",
  type: "EXAMPLE_CREATED",
  actor: "system",
  payload: { id: "example-1" },
});

const events = await listEvents(ports, "entity-1");

journalSeq from the repository is the ordering authority; timestamp is descriptive metadata only.

Public API (V0)

| Export | Role | |---|---| | appendEvent | Append via ports | | listEvents | Global journal or by entityId | | assertEventIsAppendOnly | Surface marker (no update/delete helpers) | | VersionedEvent, AppendEventInput | Domain types | | VersioningPorts / VersioningRepository | Injected adapters |

Product-specific event type taxonomies stay outside this package.

Architecture boundary

| Direction | Rule | |---|---| | Product / adapters → @jiplabs/versioning | Allowed | | @jiplabs/versioning → product packages | Forbidden |

V0 stability

Semantic behavior of the V0.1.x public API is frozen. Publication packaging may advance to npm 0.1.1 without changing domain semantics.

License

MIT © 2026 JipLabs