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. Swift package registry

Images and publishing

Swift package registry

Answer SwiftPM as a package registry over a git host. Each version tag is fetched once, kept and scanned.

  1. Settings, Registries: switch on Swift package registry.
  2. Add a Swift registry. Its address is a git host, like https://github.com.
  3. Write Swift rules: pattern apple.swift-log or apple.*, versions 1.6.1, ^1.6.0 or >=1.6 <2.
  4. Developers point SwiftPM at /swift/. See Set up SwiftPM.
  • A package is a repository. apple.swift-log is github.com/apple/swift-log. Its tags that are versions, like 1.6.1 or v1.6.1, are its releases.
  • The tag list comes from git itself, not the GitHub API, so there is no API rate limit.
  • ForgeRepo™ fetches the tag archive once, keeps and scans it, and gives SwiftPM its checksum. A tag moved later on the git host changes nothing here.
  • While it resolves, SwiftPM reads the manifest of several allowed versions, not only the one it picks. Each of those archives is fetched and kept too, because the manifest and the checksum come from it.
  • The release list holds only allowed versions. A package with none allowed is refused with the reason, and that opens a request.
  • Advisories come from OSV, which knows Swift packages by their GitHub url. Malware scanning, the kill switch, auto approve and Cache now all work.
  • Package.swift names no license, so Swift packages have none on record.
  • swift package-registry publish is refused. This registry mirrors packages.