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
  1. Home
  2. Documentation
  3. Administrator Guide
  4. CocoaPods CDNs

Images and publishing

CocoaPods CDNs

Mirror the CocoaPods CDN for pod install. The code of each pod is fetched and scanned by this box.

  1. Settings, Registries: switch on CocoaPods CDN.
  2. Add a CocoaPods registry. For the public pods use https://cdn.cocoapods.org.
  3. Write pod rules: pattern Alamofire or Firebase*, versions 5.9.1 or ~> 5.9.
  4. Developers add the source line to their Podfile. See Set up CocoaPods.
  • The CDN only describes a pod. Its code is a git tag, usually on GitHub. ForgeRepo™ fetches the tag archive itself, keeps and scans it, and the podspec it hands out points pod at that copy.
  • A pod whose code cannot be fetched as a fixed archive is refused: a git branch or commit, git submodules, svn, or a download that does not match the checksum in its podspec. Sources on an internal address are never fetched.
  • The version lists hold only allowed pods and versions, so a pod nobody approved is not found. Only a download of an unapproved version opens a request.
  • OSV has no CocoaPods feed, so pods get no advisories. Malware scanning, licenses, the kill switch, auto approve and Cache now all work.
  • A podspec can hold a prepare_command, a shell command pod runs on the developer's machine. Approving a pod approves that too.