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-remote-igit

v0.1.10

Published

Git remote helper for the native igit:// infinigit transport

Readme

git-remote-igit

Git remote helper for infinigit's native igit:// transport.

cargo install git-remote-igit
# or: npm install --global git-remote-igit
git clone igit://infinigit.com/username/repository

Git discovers the executable by its git-remote-igit name. The helper resolves human-readable repository coordinates through the infinigit directory and uses the bundled infinigit-pack bridge to synchronize canister packfiles. infinigit.com automatically selects the ICP mainnet and production directory; no environment variables or Git configuration are required for public clones. Explicit configuration remains available for local development and other infinigit installations.

The helper automatically negotiates transport capabilities with each storage shard. New shards use batched resumable pack uploads, multi-chunk downloads, changed-ref object negotiation, incremental packs, immutable local pack-index caching, and bounded adaptive concurrency. If a shard predates those APIs, the same binary falls back to the original endpoints without changing Git semantics. Set INFINIGIT_DISABLE_TRANSPORT_V2=1 to force that compatibility path, or INFINIGIT_TRANSPORT_TIMINGS=1 to print phase-level timings.

Version 3 shards additionally provide one generation-aware transport snapshot. The helper caches unchanged manifests, shares the pre-push snapshot with the post-receive publisher, reads browse objects through one binary-safe Git batch process, pipelines independent metadata updates, refreshes refs atomically, and maintains Git's multi-pack index for repositories with incremental packs.

Releases

See PUBLISHING.md for registry setup, versioning, publishing, verification, and partial-release recovery.

Tags named v<version> publish the crate and npm package and attach native Linux, macOS, and Windows binaries to a GitHub Release. Keep the versions in Cargo.toml and package.json identical before tagging. The release environment needs a CARGO_REGISTRY_TOKEN secret. npm trusted publishing should authorize infinigit-labs/git-remote-igit and .github/workflows/release.yml; an NPM_TOKEN secret can bootstrap the first publication.