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

Formats and running it

A RubyGems mirror for Bundler and gem install

Switch on RubyGems source under Settings, Registries, Package types, add rubygems.org as an upstream, and the box answers /rubygems/ for Bundler and gem install.

Send Bundler through it with a mirror, so every Gemfile keeps source "https://rubygems.org" and nothing in the project changes:

bundle config set --global mirror.https://rubygems.org https://packages.example.com/rubygems/
bundle config set --global packages.example.com your-user-name:"$REPO_TOKEN"

For plain gem install, add the box with gem sources --add and remove rubygems.org. gem keeps that address in ~/.gemrc, token included, so use a token made for that machine.

Bundler talks the compact index. Each gem's info file is rebuilt from the lines of its allowed versions, keeping the sha256 the source gave, and a .gem is refused unless it hashes to exactly that. A gem the source lists no checksum for is refused too. Gemspecs are passed on as bytes and never read.

Bundler reads the info of every dependency of every version it weighs, so a gem with nothing allowed answers with an empty version list rather than an error. Only the download of an unapproved gem is refused, with a 451 whose reason Bundler prints, and that opens a request for an approver. Rules take gem requirements like ~> 4.0 or >= 1.2, < 2, and names like rails-*.

What applies, and what does not

Rules, the kill switch, quarantine, cooling off, malware scanning (the OSV known malicious check included), license policy from the gem's license list, requests, auto approve and safe version resolution all apply. Advisories come from OSV's RubyGems feed.

Honest limits: gem push is not taken, so private gems need another home for now. Typosquat checks, provenance checks and the tree walk are not offered for gems.

packages.example.com/_admin/
The Rules page. Type, pattern, kind, version range, priority, and an optional application and environment.

In short

  • Bundler and gem install through the compact index
  • A Bundler mirror, so Gemfiles stay as they are
  • Info files rebuilt from allowed versions only
  • Every .gem checked against the source's sha256
  • Refusals as a 451 Bundler prints, with a request opened
  • No gem push yet

In the documentation

Goes well with

  • Composer and Packagist proxy Composer through Packagist. Each release is fetched once from its exact commit, scanned and kept.
  • Allow lists and block lists Whitelist or blacklist by name, scope, wildcard or version range, for every type. A blocked version is not even listed to the client.
  • Malware scanning ClamAV, a hash blocklist, your own scanner and the OpenSSF known malicious feed, on every cached file. Optionally before the first download.

One container, about two minutes

A Linux box with Docker, or one without it, and a reverse proxy for TLS. The installer does the rest and it is safe to run twice. Free, MIT licensed, nothing to sign up for.