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

Images and publishing

APT mirrors

Mirror Debian and Ubuntu archives for apt. Every package is checked and scanned.

  1. Settings, Registries: switch on APT mirror.
  2. Add an APT registry for each archive. Its address is the archive root, like https://deb.debian.org/debian. Security updates are their own archive, like https://security.debian.org/debian-security.
  3. Pick the advisory feed of its distro, like Debian:12, so its packages are checked against the right advisories.
  4. In whitelist mode, add an APT allow rule of *, then deny or kill what you do not want.
  5. Developers use the address the mirror shows, like /apt/debian/. See Set up apt.
  • By default each suite's InRelease goes out exactly as the distro signed it, and every download is checked: the rules, the kill switch, holds, advisories and cooling off.
  • With Filtered index on, ForgeRepo™ first checks the distro's signature itself, then hands out Packages files of only what the rules and the kill switch allow, for amd64 and arm64, signed with its own key. Clients trust that key with signed-by. This works for the official Debian and Ubuntu archives.
  • Every index file is checked against the SHA256 in InRelease, and every .deb against the SHA256 in its Packages file, before it is kept.
  • Advisories come from OSV, in the feed you picked, by source package: libssl3 gets the advisories of openssl.
  • The signing 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.