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

First setup

First setup checklist

The settings to review before developers start using ForgeRepo™.

  1. Change the admin password on Your account, and keep a second local admin so single sign-on problems cannot lock you out.
  2. Public address. Settings, Cache tab, Public url: set it to https://packages.example.com. Error messages and these docs use it.
  3. Name and branding. Settings, Policy tab: Name shown in the portal, a header icon and a favicon.
  4. Package types. Settings, Registries tab: switch on PyPI and container images if you need them.
  5. Upstream registries. Add Docker Hub as https://registry-1.docker.io, and any internal registries. See Upstream registries.
  6. Policy. Pick whitelist or blacklist, and consider starting in audit mode. See Whitelist, blacklist and audit mode.
  7. Tokens. Turn on Require tokens once pipelines have tokens. See Require tokens.
  8. Portal network. Allow only your office and VPN networks to reach the portal. See Portal allow list and break glass.
  9. Email. Settings, Email tab, so approvers hear about requests and admins hear about malware and kills.
  10. Single sign-on, if you use one. See Single sign-on.
1
  1. Registry mode: normal, degraded or lockdown
The dashboard is the best place to check that traffic is flowing after setup.