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

Keep bad packages out

License policy for open source packages

Each cached file has its license read from the package metadata and turned into an SPDX expression where it can be. Then three lists you control decide what happens.

npm licenses come from license or the old licenses array. PyPI licenses come from License-Expression, then License, then the trove classifiers. NuGet licenses come from the licenseExpression only, so an older package that points at a license url counts as unknown. Maven reads the pom, RubyGems the gem's license list, CocoaPods the podspec, Composer composer.json, and RPM the package header. Swift packages, APT packages and container images name no license anywhere this box reads, so they count as unknown. GPL-2.0+ becomes GPL-2.0-or-later, and "Apache Software License" becomes Apache-2.0. Nothing is guessed: SEE LICENSE IN or a pasted license text counts as unknown, with a note saying why.

Settings, Licenses has allowed, needs review and blocked, one SPDX id per line with * as a wildcard (BSD-*). In MIT OR GPL-3.0-only the better choice counts, in MIT AND GPL-3.0-only the worse part does. You also choose what a license on no list is, and what an unreadable one is.

  • off, the default, does nothing.
  • warn logs it and npm prints a LICENSE: notice during the install.
  • enforce holds review licenses in quarantine and rejects blocked ones.

Changing a list re-judges every stored license at once, with no network. A license waiver covers exactly one license on exactly those versions, so if a package changes license the waiver does not follow it.

packages.example.com/_admin/
Settings, Licenses. Three lists, and what to do about a license on none of them.

In short

  • SPDX normalization for npm, PyPI, NuGet, Maven, RubyGems, CocoaPods, Composer and RPM, nothing guessed
  • Allowed, needs review and blocked lists, with wildcards
  • OR takes the better choice, AND the worse part
  • Off, warn or enforce through quarantine
  • Changing a list re-judges everything already cached

In the documentation

Goes well with

  • Integrity alerts and quarantine A file that changes after it was first seen is held. The original keeps being served.
  • Waivers A written down, time boxed yes for one finding on one package, scoped to an app or environment.
  • Artifacts, SBOMs and lifecycle Every file stored once by SHA-256, CycloneDX and SPDX out, properties and promotion stages.

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.