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

An APT mirror for Debian and Ubuntu

Switch on APT mirror under Settings, Registries, Package types. Each APT registry you add is one Debian or Ubuntu archive, like https://deb.debian.org/debian, answered at /apt/<its name>/.

Pick the advisory feed of its distro, and in whitelist mode add an APT allow rule of *, then deny or kill what you do not want. Security updates are their own archive, like https://security.debian.org/debian-security. Clients put the mirror in their sources and the login in /etc/apt/auth.conf.d/:

# /etc/apt/sources.list
deb https://packages.example.com/apt/debian/ bookworm main

# /etc/apt/auth.conf.d/company.conf
machine packages.example.com/apt/ login your-user-name password <your token>

Two ways to hand out the index

By default each suite's InRelease goes out untouched, so apt keeps checking the distro's signature. Every package download is checked: the rules, the kill switch, holds, advisories and cooling off, then the .deb is checked against its SHA256, kept and scanned. The catch is that apt still sees every version, so it can pick one that is then refused.

Filtered index has the box check the distro's signature itself, then hand out Packages files of only what the rules and the kill switch allow, for amd64 and arm64, signed with the box's own key. Clients fetch that key from https://packages.example.com/apt/signing-key.asc into /etc/apt/keyrings/ and name it with signed-by. The key is made on first use and kept in the cache folder; if it is ever lost, every client has to fetch the new one.

What applies, and what does not

Rules, the kill switch, quarantine, malware scanning (the OSV known malicious check included), requests and auto approve all apply. Advisories come from OSV by source package, so libssl3 gets the advisories of openssl, in the feed you pick for each mirror: Debian 11, 12 or 13, or Ubuntu 20.04, 22.04, 24.04 or 26.04 LTS.

Honest limits: an APT index gives no publish times, so cooling off follows the A version with no publish time setting, which lets them through by default. The license of a Debian package is in its copyright file, not the index, so it counts as unknown under license policy. Filtered mode serves amd64 and arm64 only. Nothing is published here. Typosquat checks, provenance checks and the tree walk are not offered for APT.

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

In short

  • One mirror per Debian or Ubuntu archive, for apt
  • Distro signed InRelease untouched by default
  • Filtered index signed with the box's own key, via signed-by
  • Every .deb checked against its SHA256, kept and scanned
  • Advisories by source package, Debian 11 to 13 and Ubuntu LTS

In the documentation

Goes well with

  • RPM mirror for dnf and yum AlmaLinux, Rocky Linux and Red Hat repositories, every package checked and scanned before dnf gets it.
  • Vulnerability monitoring OSV, CISA KEV and FIRST EPSS against everything allowed and cached. npm audit answered locally.
  • Kill switch Take a package, a version range, one file hash or a whole advisory away from everyone, at once.

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.