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

S3 and Azure Blob storage for the cache

Settings, Storage keeps the cache in a bucket instead of on the box. Requests are signed on the box with the bucket's keys. No cloud SDK is installed.

Fill in the endpoint, region, bucket, an optional folder and the keys, then Save and test the bucket: it puts a small file in, reads it back and deletes it. Switching to the bucket tests it again and changes nothing if that fails. Keys can come from the environment instead, which keeps them out of the database.

New files still land on local disk first, so a download never waits on the bucket, and an uploader sends them up every minute. Every upload carries the file's SHA-256 (or MD5 for Azure, which Azure checks), and the bucket refuses bytes that do not match. Local copies to keep caps the disk, dropping the least recently used copies of files the bucket already holds. A file fetched back from the bucket is checked against its SHA-256 before any of it is served.

If the bucket cannot be reached, installs carry on from local copies and new files wait on disk until it is back.

packages.example.com/_admin/
Settings, Storage. Local disk or a bucket, and what is where.

In short

  • AWS S3 and anything S3 compatible: MinIO, R2, Wasabi
  • Azure Blob with Shared Key signing
  • Hash checked uploads and downloads
  • Local copy cap with least recently used eviction
  • Keeps working from disk when the bucket does not

In the documentation

Goes well with

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.