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

Security protections

Quarantine and integrity alerts

Files held for review, and files whose contents changed after they were first seen.

A file is held when malware scanning, provenance, license rules, an integrity alert, a person, or a new publish says it needs a look. Quarantine (Settings, Policy) decides what developers get meanwhile:

ModeHeld files
permissive (default)Still served, with a QUARANTINE warning printed by npm.
strictRefused with a 403 and left out of metadata.
any modeRejected files are always refused.

release serves the file normally. reject refuses it for good. Holds belong to the file itself, so purging and downloading it again does not escape one.

Integrity alerts

The first copy of a file wins. If npm or PyPI later publish a different hash for the same version, or a download returns different bytes, ForgeRepo™ raises an integrity alert, holds the file and keeps serving the original bytes. On Integrity alerts, accept takes the new file and keep original dismisses the alert.

Careful

A changed file for a version that was already published is a classic sign of a compromised registry account. Check before you accept.