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. Developer Guide
  4. Set up SwiftPM

Swift packages

Set up SwiftPM

Point SwiftPM at the ForgeRepo™ package registry and log in with your token.

Tell SwiftPM to use ForgeRepo™ as its package registry, then log in with your user name and your token as the password:

Set up SwiftPM to use ForgeRepo™
$ swift package-registry set --global https://packages.example.com/swift/
$ swift package-registry login https://packages.example.com/swift/ --username your-user-name --password "$REPO_TOKEN" --no-confirm
Login successful.

Credentials have been saved to netrc file.
Registry configuration updated.

Captured by running these commands against a real ForgeRepo™.

  • --global sets it for every package on your machine. Leave it out to set it for one package only.
  • The login is saved in ~/.netrc on Linux and in the keychain on a Mac. It needs https.
  • A package is named by its identity, scope.name. apple.swift-log is github.com/apple/swift-log.
  • SwiftPM warns that a source archive is not signed. ForgeRepo™ does not sign archives. SwiftPM checks each one against the checksum packages.example.com gives it.

Name dependencies by identity in Package.swift, and in a product use the identity as the package name:

Resolve and build a package
$ cat Package.swift
// swift-tools-version:5.9
import PackageDescription

let package = Package(
  name: "Shop",
  dependencies: [
    .package(id: "apple.swift-log", from: "1.6.0")
  ],
  targets: [
    .executableTarget(name: "Shop", dependencies: [
      .product(name: "Logging", package: "apple.swift-log")
    ])
  ]
)
$ swift package resolve
Computing version for apple.swift-log
Computed apple.swift-log at 1.6.4 (1.41s)
Fetching apple.swift-log
warning: 'apple.swift-log': apple.swift-log version 1.6.4 source archive from https://packages.example.com/swift/ is not signed
Fetched apple.swift-log from cache (0.06s)
$ swift build 2>&1 | tail -2
[15/16] Linking Shop
Build complete! (4.92s)

Captured by running these commands against a real ForgeRepo™.

Note

A dependency written as a GitHub url still goes to GitHub. Add --replace-scm-with-registry to swift package resolve or swift build, and SwiftPM asks packages.example.com for it instead.