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. Gem sources

Images and publishing

Gem sources

Mirror rubygems.org or a private gem source for Bundler and gem install, with the same checks as the other types.

  1. Settings, Registries: switch on RubyGems source.
  2. Add a RubyGems registry. For rubygems.org use https://rubygems.org.
  3. Write gem rules: pattern rack or rails-*, versions 3.1.8, ~> 3.1 or >= 3.0, < 4.
  4. Developers set a Bundler mirror. See Set up Bundler.
  • Every gem has to match the sha256 its source lists for it. A gem with no listed checksum, or a different one, is refused and not kept.
  • The version list a gem gets (/info) holds only allowed versions, so Bundler resolves to an allowed one.
  • Bundler looks at the version list of every gem it might need, old versions included. A gem with nothing allowed shows no versions, so the resolver picks versions that do without it. Only a download of an unapproved gem opens a request.
  • A refused download is answered with a 451 status, the one Bundler prints the reason for.
  • Every gem is scanned for malware, checked against OSV, has its license read from rubygems.org, and waits out cooling off. Auto approve and Cache now work for gem rules too.
  • gem push is not taken yet.