Hey,
I've released PkgLift 0.6.0. It's an open-source Swift tool for moving supported CocoaPods dependencies to SwiftPM in native Xcode projects. You get a plan to look through first, and dependencies it can't safely map stay with CocoaPods.
The recent work has been about pods that don't already have a Swift package. 0.5 added an in-memory model for Podspec JSON. In 0.6 I've started working out what extra information would be needed to turn that into a package: selected source files, a target and the library product it exposes.
This part is still early. It's a library API that currently only covers one synthetic Swift library, using information supplied by the caller. It doesn't check the real files or generate Package.swift, and the CLI's migration support hasn't expanded.
I'm interested in getting those assumptions right before taking it further. If you've converted a pod to SwiftPM yourself, what was the part that a tool would have been most likely to get wrong? Source selection, resources, build settings, or something else?
You can try the existing migration tool with:
brew install Alexsvensson99/tap/pkglift
Release: Release PkgLift v0.6.0 · Alexsvensson99/PkgLift · GitHub