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

@volter/world-core

v2.0.35

Published

The kernel of Volter World: one log per twin, branches as pointers, checkpoints, the fold that keeps a twin current, the head that performs a write against the vendor, references, and the git plane. A twin package builds on it; the runtime serves it.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

volter-oliveriovolter-oliverioaaronvolteraaronvolter

Keywords

twinlocalmockmirrorsimulatorfixturestestingsdkapilocalstackevent-sourcingkernel

Readme

@volter/world-core

The shared state kernel and vendor-independent runtime libraries used by @volter/twin-<vendor>. The product CLI and SDK are in @volter/world.

State and branching

The model is the canonical explanation: one logical log, checkpoints, a branch's parent position and its own entries, and simulated or real execution at the head. Push lands entries in a parent; deploy performs them against the vendor and records receipts. The Git-inspired verbs do not imply staging, commits or a Git object database.

The file store has inherited entries (events.jsonl), branch entries (actions.jsonl), branch.json, a fetched URL-parent cache (origin.jsonl) and checkpoints. These are storage segments of that model, not independent observed-state and local-action truth systems. See log.ts for the format and state-system.ts for execution. Payloads use the blob storage contract.

Building a twin

A protocol-2 twin implements its vendor's request/response semantics while the shared kernel owns log ordering, checkpoints, branching and the head's state system. Use the tree readers and write path exported by src/index.ts; do not reconstruct a serve-time view by folding the log or use removed v1 confirmation/suppression APIs.

Architecture owns the boundaries and adding a twin owns the implementation and verification process. Package protocol standing is recorded in the generated index. Conformance tooling is a development dependency in @volter/world-tooling.