Swift Package Index has joined Apple. The announcement landed Monday on the project’s own blog, co-signed by Ted Kremenek of Apple along with founders Dave Verwer and Sven A. Schmidt. The date was June 23, 2026. Three years after Apple first sponsored the service, the independent project has become part of the company that created the Swift language itself.
Developers didn’t see the site go dark. No immediate redesign appeared. The index still lists more than 11,000 packages, runs compatibility tests, and hosts documentation. Yet the shift carries weight. Apple now owns the de facto discovery layer for Swift’s open-source libraries. The move signals how seriously the company takes the health of its package ecosystem.
The Swift Package Index began in 2020 as an answer to a gap. Apple had shipped the Swift Package Manager in 2015. Xcode gained native support in 2019. But developers still struggled to find trustworthy code. Verwer and Schmidt built a search engine that went beyond links. Their site cloned repositories, analyzed manifests, examined Git history, and surfaced signals such as license choice, maintenance activity, and release cadence. Swift.org noted in 2023 that the index had become a popular destination for exactly these reasons.
Then came the builds. The team set up automated testing across platforms and Swift versions. Early on the system handled about 5,000 builds a day. By last year that number had exploded. The announcement cites more than 3.5 million compatibility builds processed in a single year. Support expanded from the original macOS, iOS, tvOS, watchOS, and Linux targets to visionOS, WebAssembly, and Android. Package authors and consumers gained concrete data before they added a dependency.
Documentation followed. The index began generating and hosting versioned DocC pages for free. More than 300 packages opted in during the early phase. Storage demands grew quickly. All of it ran on community sponsorship and the founders’ own effort. The project itself is written in Swift, built on Vapor, and has merged more than 1,200 pull requests since launch.
From sponsorship to ownership
Apple’s initial sponsorship arrived in March 2023. The Swift.org announcement praised the index as a valuable resource. Verwer and Schmidt expressed pride that Apple had joined other sponsors. They hoped the support would keep the site running for years. Few expected full integration so soon.
Now the relationship has deepened. The joint post states the move “allows us to build on its strong foundations while preserving its vision and expertise. Together, we’re building a comprehensive package registry to serve the Swift community’s evolving needs.” The language is careful. Continuity comes first.
For developers using the site today, nothing changes immediately. Search still works. Compatibility matrices remain. Documentation links stay live. Package authors see no shift in how their work appears. The post repeats the promise: “There are no immediate changes in how your packages are indexed or presented, or how your documentation is hosted.”
Yet the future holds new capabilities. The announcement flags plans for package signing and identity features. These additions would address security and trust at a deeper level than metadata alone can provide. Apple engineers will contribute code alongside the existing open-source community. The project stays open source. Contributions remain welcome.
Observers on X reacted quickly. One developer posted simply, “SPI being part of Apple makes so much sense.” Another noted the Hacker News discussion that followed the announcement. The tone mixed relief with curiosity about what comes next. No one expected the site to vanish. Many wondered how deeply Xcode integration might expand.
The timing matters. Swift continues to gain adoption beyond Apple platforms. Server-side use grows. VisionOS and Android support in the test matrix already reflect that broadening reach. A company-backed registry could accelerate standards around security scanning, provenance, and long-term maintenance. But it also concentrates influence. Previous attempts at centralized catalogs, such as IBM’s short-lived effort, never gained traction. The index succeeded because it stayed focused on developer decision-making rather than pure distribution.
Verwer has long championed better dependency hygiene. His iOS Dev Weekly newsletter, which he recently handed off to focus fully on the index, frequently highlighted package quality. Schmidt’s independent work brought deep technical execution. Their combined effort created something Apple apparently decided was too important to remain outside.
Scale was always the challenge. Running millions of builds demands infrastructure. Storage for documentation grows without bound. Monitoring systems track the build fleet. The joint announcement promises greater investment in these areas. “With Apple’s support, we’re able to invest deeply in helping developers make better decisions about their package dependencies, operate at greater scale, and take on the next set of challenges with confidence.”
So what should teams do now? Continue using the index. Its data still informs choices. Watch for the promised updates on new features. Package authors should keep opting into documentation builds and monitor the blog for guidance on signing. Contributors can still open pull requests. The open-source repository remains public.
The broader Swift community has reason for optimism. Discovery and trust have long been pain points. A well-resourced team inside Apple, paired with the original creators and ongoing external input, stands a strong chance of delivering meaningful progress. But success will depend on whether the new structure preserves the independent spirit that made the index valuable in the first place.
That spirit shows in small details. The podcast “Swift Package Indexing” continues. Community package picks still appear. The blog will keep sharing updates. Ted Kremenek, Dave Verwer, and Sven A. Schmidt signed the announcement together. The names side by side suggest collaboration rather than absorption.
Apple has bet on open source before. Swift itself, the Package Manager, and numerous frameworks demonstrate the pattern. Bringing the index inside folds another critical piece into that strategy. The registry they build together could become the trusted hub for Swift code for the next decade.
Developers will judge it by results. Faster feature delivery. Better security signals. Clearer compatibility data. Easier evaluation of maintenance risk. If those arrive while the site stays familiar and the code stays open, the transition will count as a success. The announcement sets that direction. The months ahead will reveal how closely reality matches the stated goals.
WebProNews is an iEntry Publication