PkgLift
Move supported CocoaPods dependencies to SwiftPM safely
Start new thread

PkgLift - Move supported CocoaPods dependencies to SwiftPM safely

by•
PkgLift helps native Apple teams plan and apply conservative CocoaPods-to-SwiftPM migrations. It moves only dependencies backed by verified mappings, preserving uncertain cases for review. v0.10.0 runs on macOS 14+ Apple Silicon.

Add a comment

Replies

Best
Maker
📌

Hi Product Hunt, I'm Alexander, the independent developer behind PkgLift.

I built PkgLift to make CocoaPods-to-SwiftPM migrations easier to review. It inspects your Podfile, lockfile and Xcode project, then produces a plan. Preview first; apply only with an explicit command. Dependencies without enough evidence stay under CocoaPods for review.

This launch uses the published v0.10.0 release for macOS 14+ on Apple Silicon. The demo replays actual terminal output, shows the Podfile change and includes separate before/after Xcode build results for the same small Swift/Objective-C SDWebImage fixture. Both builds passed with the same iOS 15.0 target override; app-source hashes matched. This is build and structure verification, not runtime testing.

CryptoSwift is a separate example of the work behind this release. A matching package name was not enough: the supported Swift/iOS 15+ path needed exact package and product checks, source and privacy-resource evidence, and CocoaPods/SwiftPM consumer builds. The automatic path stays deliberately narrow.

I used GPT-6 Astra in Codex during development and validation. It helped me carry that demanding verification work through as an independent developer. PkgLift itself runs locally without an OpenAI API key.

Apple developers: what would make a partial migration useful for your project?

Source and release:

CryptoSwift validation:

OpenAI
GPT-6 Astra Challenge
How did Astra change the scope or ambition of what you built?
Maker
CryptoSwift made the challenge concrete: a matching Swift package name was not enough to justify an automatic migration. I used GPT-6 Astra in Codex during PkgLift's development and validation work. For v0.10.0, that work included checking the exact package and product, Swift/iOS 15+ consumer support, source preservation and the privacy resource. The mapping was admitted only after CocoaPods and SwiftPM consumer builds and a complete migration-and-build pilot. Unproven configurations remain outside the automatic path. Astra helped me carry a demanding validation workflow through as an independent developer. The result is a deliberately narrow, reviewable migration path rather than a blanket compatibility claim. PkgLift runs locally without an OpenAI API key.