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

Watch it work

Two walkthroughs of the real screens

The first shows an admin setting ForgeRepo™ up, in the order the screens are actually used. The second is the bad morning: a popular package has just shipped malware. Press play, or step through either one yourself.

Setting it up

From the first sign in to the first approval

Registries, rules, tokens and the first request a developer opens, in the order an admin actually uses them.

https://packages.company.internal/_admin/
Step 1

Setting ForgeRepo™ up 0:00 / 0:00

A guided walkthrough built from real screenshots, not recorded video. Use the arrows, or the left and right keys, to go at your own pace.

The bad morning

A popular package just shipped malware. Now what?

Kill it for everyone in one form. See every application, environment and pipeline that pulled it. Stop fetching anything new if the whole ecosystem is burning. All of it on the record.

https://packages.company.internal/_admin/
Step 1

Responding to a compromised package 0:00 / 0:00

A guided walkthrough built from real screenshots, not recorded video. Use the arrows, or the left and right keys, to go at your own pace.

Try it on your own server

Everything in these walkthroughs runs on one container. The installer takes about two minutes on a bare server, and it is free.