The Swift Package Index Blog

Recognising Package Authors

Posted Wednesday, December 14, 2022.

When we launched this site back in June 2020, one of the features on the “must be done before launch” list was support for showing who wrote each package. Not just a GitHub username but the names of the primary contributors.

We didn’t quite get that feature in for launch, and then other things took priority as we started dealing with real users and the day-to-day running of the site. Then we tackled build compatibility, documentation, and many other features.

We never returned to author information. Until now!

The Swift Package Index project participated in the Swift Mentorship Program again this year, and we’re delighted to say that Javier Cuesta has done outstanding work resurrecting this feature from the depths of the issue backlog!

The Swift Package Index site showing author metadata for the fastlane package.

By default, we try to determine who has contributed the most to a package and include their name(s). Then, if there are more contributors, we’ll say how many.

All this information comes from git history, and the automated mechanism and algorithm we have used may not get it right. With that in mind, we also allow package authors to override the display of author information through the .spi.yml file.

Adding a top-level metadata key with an authors key below it will override any automatic author information entirely. For example:

version: 1
metadata:
  authors: “Written by Person One, Person Two, and other contributors.”

We want to thank everyone who contributes to open-source software, and we hope this feature helps authors get credit for their efforts.

We’d also like to thank Javier for his hard work and always-positive attitude on this feature. Every aspect of working with him was a pleasure, and this feature only exists today because of his efforts.


The Swift Package Index is a search engine for Swift packages with one goal. To help you make better decisions about dependencies. For more information, the best place to start is with the Frequently Asked Questions.