The Swift Package Index helps you make better decisions about the dependencies you use in your apps.
Code of Conduct
All participation in this project, whether contributing code, communicating in discussions or issues, or pull requests, is subject to our code of conduct. Please read the Code of Conduct before contributing.
Funding and Sponsorship
The Swift Package Index is a community project that would not be possible without the support of its sponsors. Thank you to everyone who supports this project!
Corporate and Infrastructure Sponsors
Thank you to all of our corporate sponsors for their support.
- Stream: Build reliable, real-time, in-app chat and messaging in less time.
- Emerge Tools: Monitor app size, improve startup time, and prevent performance regressions.
- MacStadium: Virtualized and bare-metal Macs in the cloud.
- Microsoft Azure: Unify management of all your resources with Azure tools and guidance.
The support of this community means everything to us. Thank you to everyone who sponsors this project via GitHub sponsors.
There are many ways to contribute to the Swift Package Index. Whether it's helping to promote the site, suggesting or discussing a new feature, reporting a bug if you find one, through to helping with bug fixing, or the design/development of the software, we'd love to have you as a contributor.
To keep our issues list under control, most bug reports or feature requests work best started as a discussion in our forum. From there, we can promote it into an issue and start work on a pull request. We have plenty of open issues if you'd like to get started. We've also tagged some with a good first issue label.
We also have a Discord server. If you'd like to join, please use this invite!
Running the Project Locally
The best place to start is our in-depth guide to setting up the Swift Package Index for local development! If you run into any problems, please start a discussion or join us on Discord.
Contributor License Agreements
The Swift Package Index is licensed under the Apache 2.0 license. Before we can accept your contributions, you'll need to sign a standard Apache 2.0 Contributor License Agreement. We will organise this during your first pull request.