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

When something goes wrong

Who has it: consumers of every package and version

Consumers answers the question every incident starts with: who has this?

Search for a package, a version or range, a file by its SHA-256, or an advisory by its CVE, GHSA or PYSEC id. The answer lists the applications and environments that took it with production flagged, the developers and CI pipelines, the addresses, how many downloads, and the first and last download of each.

It works because every token carries an application and an environment, and every download that was actually served is folded into one small row per version per consumer. That record is kept for a year by default, much longer than the raw traffic log, and it is written when it happens: if a token is later revoked or moved, the rows keep saying what was true at the time.

SBOM of an application turns the same record into a document: every version an application downloaded in an environment, with the SHA-256 of each file still cached, in CycloneDX. That is the file to send the auditor who asks what is in production.

packages.example.com/_admin/
Consumers. Where a package is, and every consumer of it.

In short

  • Search by name, range, SHA-256 or advisory id
  • Applications and environments, with production flagged
  • Developers, pipelines, addresses, counts, first and last seen
  • Kept for a year by default, set to forever if you like
  • SBOM of an application from what it actually downloaded

In the documentation

Goes well with

  • Kill switch Take a package, a version range, one file hash or a whole advisory away from everyone, at once.
  • Artifacts, SBOMs and lifecycle Every file stored once by SHA-256, CycloneDX and SPDX out, properties and promotion stages.
  • Tokens, apps and environments Every download is tied to a token, an application and an environment. Rules can be scoped to them.

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.