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

Formats and running it

A CocoaPods CDN mirror

Switch on CocoaPods CDN under Settings, Registries, Package types, add https://cdn.cocoapods.org as an upstream, and the box answers /cocoapods/ as a CocoaPods CDN.

Put the box at the top of the Podfile in place of the default source, and give pod the login in ~/.netrc:

source 'https://packages.example.com/cocoapods/'
platform :ios, '15.0'

target 'App' do
  pod 'Alamofire', '~> 5.9'
end
machine packages.example.com login your-user-name password <your token>

The shards pod reads list only the pods and versions the rules allow. Rules take names like Alamofire or Firebase* and requirements like ~> 5.9.

The CDN only describes pods. Their code usually lives in a git tag on GitHub, so a podspec is handed out with its source pointed at the box. The box fetches the code itself, as the tag's archive from GitHub or GitLab or the http archive the podspec names, checks it against any checksum the podspec gives, keeps and scans it, and serves that copy. pod never goes to GitHub for it.

What applies, and what does not

Rules, the kill switch, quarantine, malware scanning, license policy from the podspec, requests and auto approve all apply.

Honest limits: OSV has no CocoaPods feed, so pods get no advisories, no safe version resolution and no known malicious check. The CDN gives no publish times, so cooling off follows the A version with no publish time setting, which lets them through by default. A source that cannot be fetched as a fixed archive (a branch, a commit, submodules or svn) is refused with the reason, and a source on an internal address is never fetched. Pods are not published here. Typosquat checks, provenance checks and the tree walk are not offered for pods.

packages.example.com/_admin/
The Rules page. Type, pattern, kind, version range, priority, and an optional application and environment.

In short

  • A CocoaPods CDN for pod install and pod update
  • Shards list only the pods and versions the rules allow
  • Pod code fetched by the box, checked, scanned and kept
  • Branch, commit, submodule and svn sources refused
  • No advisories: OSV has no CocoaPods feed

In the documentation

Goes well with

  • Swift package registry SwiftPM through an SE-0292 registry that serves GitHub tags as releases, each archive scanned and kept.
  • Allow lists and block lists Whitelist or blacklist by name, scope, wildcard or version range, for every type. A blocked version is not even listed to the client.
  • Malware scanning ClamAV, a hash blocklist, your own scanner and the OpenSSF known malicious feed, on every cached file. Optionally before the first download.

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.