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. Registry modes: degraded and lockdown

Incident response

Registry modes: degraded and lockdown

Slow or stop what comes in from outside during an ecosystem wide incident or an outage.

NormalFetches anything the rulesallowDegradedNo brand new names arefetched. Names already heldstill refreshLockdownNothing is fetched. Onlyfiles on disk are offered.Quarantine acts strictraiseraise

Change the mode on the Dashboard, under Registry mode. A reason is required, every change is audited and admins are emailed. Approvers can raise the mode. Only admins can lower it.

When the upstream registry is down

  • npm and PyPI metadata is served from cache for up to Seconds we will serve stale metadata if upstream is down (default 7 days).
  • Files already cached are always served.
  • Image tags confirmed within that window keep working. Pulls by digest of kept images never need Docker Hub.
  • In lockdown, or with Upstream registry enabled off, kept copies are served at any age.

Tip

Before a planned outage, cache what matters: allow rules with exact versions or tags, then Cache now on Rules.