Product

Overview

How it works Watch it work All 35 features Screenshots How ForgeRepo™ is secured

Keep bad packages out

Malware scanning Typosquat detection Dependency confusion protection Cooling off new releases Allow lists and block lists

When something goes wrong

Kill switch Who has it Lockdown and degraded modes Vulnerability monitoring

Developers and approvals

Requests and auto approve Check, walk and review Waivers Dry run
Formats

Languages

Private npm registry PyPI proxy and private index Private NuGet feed and proxy Maven repository proxy RubyGems mirror Composer and Packagist proxy

Apple, containers and Linux

CocoaPods CDN mirror Swift package registry Docker registry mirror RPM mirror for dnf and yum APT mirror for Debian and Ubuntu

Use it as

An npm firewall Artifacts, SBOMs and lifecycle More than one node SSO, roles and allow lists
Learn

Guides

Learn secure development Secure coding Secure pipelines Unsafe vs safe Security and development

Supply chain

Supply chain attacks, 2016 to 2026 Software supply chain security
Compare Side by side, all four ForgeRepo™ vs JFrog ForgeRepo™ vs Sonatype ForgeRepo™ vs Cloudsmith
Docs

Start

Getting started Download All documentation Questions

For developers

npm setup pip setup docker login Push a Docker image CI basics

For administrators

First setup Rules and their order Six incidents, walked through Backup and upgrade
Pricing Install it
  1. Home
  2. Documentation
  3. Administrator Guide
  4. Upgrades, health and high availability

Operations

Upgrades, health and high availability

Upgrade safely, roll back, monitor health, and run more than one node.

on the server

./setup.sh --upgrade          # pull, keep the old image as npm-repo:previous, rebuild, restart, wait for health
curl -s https://packages.example.com/_health    # {"ok":true}, or a 503 if the database is unreachable

# roll back, if the database was not upgraded to a newer MariaDB
docker tag npm-repo:previous npm-repo:latest && docker compose up -d
  • --upgrade refuses to run over local edits and never touches .env or the data directory. Database changes run automatically at start.
  • Plain docker compose up -d does not rebuild. Use --build or the upgrade script.
  • Hard refresh the portal after an upgrade. The page is cached for five minutes.

More than one node

  • Point every node at one MariaDB with DB_HOST. Rules, users, sessions, tokens, settings, allow lists and findings are shared.
  • Cached files are not shared unless you use S3 or Azure storage. Otherwise sync the cache directory and run Check for drift after a failover.
  • Settings reach other nodes within 30 seconds, rules within 5. Background jobs run on every node, so active and passive is recommended.

Reverse proxy

Put nginx or another proxy with TLS in front, using the example in nginx/npm-repo.conf.example. The proxy must set X-Forwarded-For to the client address, and the container port should only listen on 127.0.0.1.