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. RPM mirrors

Images and publishing

RPM mirrors

Mirror distro repositories like AlmaLinux 9 BaseOS for dnf and yum. Every package is checked and scanned.

  1. Settings, Registries: switch on RPM mirror.
  2. Add an RPM registry for each repository. Its address is the folder that holds repodata/, like https://repo.almalinux.org/almalinux/9/BaseOS/x86_64/os.
  3. Pick the advisory feed of its distro, like AlmaLinux:9, so its packages are checked against the right advisories.
  4. In whitelist mode, add an RPM allow rule of *, then deny or kill what you do not want. A distro has thousands of packages.
  5. Developers use the address the mirror shows, like /rpm/almalinux-9-baseos/. See Set up dnf and yum.
  • By default the index goes out exactly as the distro signed it, so clients keep checking its signature. Every download is checked: the rules, the kill switch, holds, advisories and cooling off.
  • With Filtered index on, the index lists only what the rules and the kill switch allow, so dnf never picks a refused version. The distro did not sign that index, so clients must set repo_gpgcheck=0. Package signatures are still checked.
  • Every package is checked against the checksum in the repository index before it is kept, and every metadata file against the checksum in repomd.xml.
  • Only the repodata and the packages the index lists are served. Nothing else of the tree is.
  • Advisories come from OSV, in the feed you picked for the mirror: ALSA for AlmaLinux, RLSA for Rocky Linux, RHSA for Red Hat.