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

CI pipelines

Pipelines: the short version

One token per pipeline, kept in the pipeline secrets, and the same commands as your laptop.

  1. Make a token just for the pipeline, named after it, like storefront-ci. Ask an admin to place it in the application and environment it builds for.
  2. Save it as a secret in your CI system, for example REPO_TOKEN.
  3. Use the same setup commands as on your laptop, reading the token from that secret.
  4. Use npm ci, pip install -r requirements.txt or pinned image tags, so builds install exactly what you tested.

Tip

When a pipeline install is blocked, the error line in the build log says what and why. The package is often already waiting in Requests for an approver.