I spent about a week, writing this[0].
It’s a special UIKit map package, designed to be integrated into SwiftUI, as map support is a big SwiftUI Achilles heel.
I have integrated it into another package (a SwiftUI admin tool, that isn’t public), and it works exactly as I planned.
I often do this kind of thing. If I can break some module out of my work, and publish it, I spend the extra time, polishing and documenting it. No one else really cares, but it forces me to do a really good job, so I get an extremely high-Quality component, that I don’t have to worry about, later.
Interesting! I've recently plumped for UIKit (with bits of SwiftUI dropped in) for a new mapping app because, as you say, SwiftUI map support is virtually non-existent. Have you thought about adding Maplibre support as an alternative to MapKit?