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

Swift packages

When SwiftPM cannot get a package

A package nobody approved is refused, and swift prints why.

A package nobody approved yet is refused, and SwiftPM prints the reason:

What a package nobody approved looks like
$ swift package resolve
error: failed fetching apple.swift-collections releases list from https://packages.example.com/swift/: server error 403: apple.swift-collections is not approved on this registry. Reason: not on the whitelist. Ask for it at https://packages.example.com/_admin. It is being scanned and checked now, and approved by itself if it comes back clean. Try again in up to 10 minutes.

Captured by running these commands against a real ForgeRepo™.

Asking for it this way already opened a request. You can also ask on the Requests page.

Note

Only tags that are versions, like 1.6.1 or v1.6.1, are releases. A branch or a commit can not come through ForgeRepo™.