SSwift Registry.
Get started
SWIFTPM PACKAGE REGISTRY

Turn Git-clone dependency resolution
into immutable, auditable artifacts

Swift Registry is a package registry and delivery platform for SwiftPM. Replace slow Git-based dependency resolution with fast, immutable, auditable package artifacts.

Example public packages
apple.swift-logvapor.vaporpointfreeco.swift-composable-architecture
Terminal — one-command setup
$ swift package-registry set \
https://registry.swiftregistry.io
// Package.swift
.package(id: "mycompany.design-system", from: "1.2.0")
$ swift package resolve
Resolved dependencies from registry
The problem

At scale, Git-based SwiftPM dependencies are slow, mutable, and hard to audit

Slow resolution

Every dependency is a full Git clone. With many packages, CI spends minutes just resolving.

Mutable tags

Git tags can move, be deleted, or rewritten. No guarantee yesterday’s 1.2.0 equals today’s.

No audit trail

No central record of what was published or changed, or by whom. Supply-chain verification is hard.

The solution

Registry-based immutable source archives

Immutable, checksum-verified releases with access control and CI acceleration.

01

Immutable releases

Once published, a version never changes. Sealed with a SHA-256 checksum.

02

CI acceleration

Cached artifact downloads instead of full Git clones speed up resolution in CI.

03

Access control

Access tokens with read and publish scopes secure your private packages. RBAC and SSO are on the roadmap.

04

Audit trail

Every publish, token, and permission change is logged. Built for regulated environments.

How it works

Three lines is all it takes

  1. Set the registry

    Register the registry with SwiftPM in a single command.

  2. .package(url:) → .package(id:)

    Swap Git URLs for package identifiers.

  3. Resolve & build as usual

    SwiftPM handles the rest. Works in Xcode and the CLI.

Package.swift
immutable · checksum verified
Supply-chain security

Verifiable by default

Immutable releases

Published versions can’t be overwritten or moved.

Checksum verification

Every artifact is verified with a SHA-256 checksum.

Hashed credentials

Tokens are stored only as hashes, never in plaintext.

Audit log

Every publish, token, and permission change is recorded.

Adopt it in a single afternoon

Start free. No credit card required.