Git2Npm

A private npm registry that serves packages from Git repositories. No npm publish needed — tag in Git and install from here.

Features

Git as source of truth — Packages are built from your Git repos. Push a tag (e.g. v1.0.0) and the registry publishes that version as latest.
npm-compatible — Use npm install, yarn, or pnpm with this registry. Scoped and unscoped packages supported.
Branch and commit builds — Install by tag (e.g. @dev) or by exact version for reproducible installs.
Web UI — Browse packages, view versions, README, and changelog.

How to use

Point your package manager at this registry, then install by name (and optionally by tag or version).

1. Configure the registry (use this server’s URL):

npm config set registry https://npm.pirchheim.net/
# or for a single install:
npm install --registry=https://npm.pirchheim.net/

# pnpm:
pnpm config set registry https://npm.pirchheim.net/

2. Install packages — by latest, by version, or by our additional tags (see below).

npm install my-package           # latest (from Git tags)
npm install my-package@1.0.0     # specific version
npm install my-package@dev       # latest from dev branch (if configured)

Additional tags and versions

Besides standard semver and latest, this registry may expose:

latest — Latest release from Git tags (e.g. v1.0.0).
Branch dist-tags (e.g. dev, develop) — Latest commit on a branch. Install with my-package@dev (or the tag configured for that package).
Commit versions — Install at an exact Git commit: my-package@0.0.0-commit-<shortSha> when that version is available. When commit builds exist, my-package@commit-latest points to the latest commit build.

Get access

Packages are available only to signed-in users. Sign in with your registry token to view and install packages.