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

@reticulum/rngit

v0.9.13

Published

Git repositories over Reticulum — an rngit-compatible transport and client for isomorphic-git

Readme

@reticulum/rngit

rngit (Reticulum Git) transport for isomorphic-git.

Clone, fetch from and push to rns:// Git remotes served by an rngit node — from Node.js, Deno, Bun or the browser.

Example: clone, commit, push

import fs from "node:fs";
import git from "isomorphic-git";
import { AutoInterface, LocalClientInterface } from "@reticulum/node";
import { Reticulum } from "@reticulum/core";
import { RngitClient, clone, push } from "@reticulum/rngit";

// Connect to the mesh however your platform allows. Here: a local rnsd
// shared instance, falling back to AutoInterface.
const rns = new Reticulum();
const shared = await LocalClientInterface.connectToSharedInstance();
if (shared) {
  rns.addInterface(shared, true);
} else {
  const auto = new AutoInterface({ name: "auto" });
  await auto.connect();
  rns.addInterface(auto, true);
}

// The client ties the mesh connection to one rngit remote and holds your
// Reticulum identity, which the node needs to see for push permissions.
const url = "rns://adafb3153efd4d96d532568a5208b3b5/reticulum/reticulum-js";
const client = new RngitClient({ url, reticulum: rns });

// Clone into a working directory. The remote stays recorded as `rns://…`
// in .git/config, so later fetches and pushes only need `dir` and the client.
await clone({ fs, dir: "./reticulum-js", url, client });

// Make a commit.
fs.writeFileSync("./reticulum-js/EXAMPLE.md", "# Hello from rngit\n");
await git.commit({
  fs,
  dir: "./reticulum-js",
  message: "Add EXAMPLE.md",
  author: { name: "Your Name", email: "[email protected]" },
});

// Push it back over the mesh.
await push({ fs, dir: "./reticulum-js", ref: "main", client });

The push requires w (write) permission for your Reticulum identity on the node — see the rngit node's access configuration.

Fetches pick up new commits the same way:

import { fetch } from "@reticulum/rngit";

await fetch({ fs, dir: "./reticulum-js", client });

And RngitClient.deleteRef("refs/heads/…") removes a remote ref (/git/delete).

Where the client identity lives

With a reticulum instance backed by a storage adapter, the client identity persists between runs:

import { FileStorageAdapter } from "@reticulum/node";
import { Reticulum } from "@reticulum/core";
import { RngitClient, clone } from "@reticulum/rngit";

const rns = new Reticulum({ storageAdapter: new FileStorageAdapter("~/.reticulum-js") });
await clone({
  fs,
  dir: "./reticulum-js",
  url: "rns://adafb3153efd4d96d532568a5208b3b5/reticulum/reticulum-js",
  client: new RngitClient({
    url: "rns://adafb3153efd4d96d532568a5208b3b5/reticulum/reticulum-js",
    reticulum: rns,
  }),
});

See the package changelog for the current implementation state, and the rngit section of the Reticulum manual for the node-side protocol.