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. Whitelist, blacklist and audit mode

Rules and approvals

Whitelist, blacklist and audit mode

Choose whether unknown packages are blocked or allowed, and how to switch safely.

12
  1. Whitelist or blacklist
  2. Serve everything and record what would be blocked
ModeNo rule matchesBest for
whitelistBlockedThe strongest protection. Every package needs an allow rule.
blacklistAllowedGetting started. Only deny rules and the security checks stop anything.

Audit only (learning mode)

With Audit only on, everything the rules would block is served anyway and recorded as "would have blocked". A request is opened for each package with the exact versions used. The kill switch still blocks in audit mode. Safe resolution, cooling off, license holds and lookalike blocking do not.

  1. Turn on Audit only in whitelist mode and point your pipelines at packages.example.com.
  2. Let a few weeks of normal builds run.
  3. On Requests, approve what your teams really use. Tick several and use Approve selected.
  4. Check Traffic with Show: would have blocked until it is quiet.
  5. Turn Audit only off.

Tip

Use Dry run before a big rule change to see who would be affected. See Dry run.