Metrics not applied
Very Popular +30
The popularity of a project is a useful way of discovering if it is useful, and well maintained.
Popular +10
A popular library means there can be a community to help improve and maintain a project.
Supports Swift Package Manager +15
Supports Apple's official package manager for Swift.
Great README +5
A well written README gives a lot of context for the library, providing enough information to get started.
Has a CHANGELOG +8
CHANGELOGs make it easy to see the differences between versions of your library.
Built in Swift +5
Swift is where things are heading.
Built in Objective-C++ -5
Usage of Objective-C++ makes it difficult for others to contribute.
Uses GPL -20
There are legal issues around distributing GPL'd code in App Store environments.
Uses WTFPL -5
WTFPL was denied as an OSI approved license. Thus it is not classed as code license.
Has Tests +4
Testing a library shows that the developers care about long term quality on a project as internalized logic is made explicit via testing.
Test Expectations / Line of Code +10
Having more code covered by tests is great.
Lines of Code / File -8
Smaller, more composeable classes tend to be easier to understand.
Post-1.0.0 +5
Has a Semantic Version that is above 1.0.0
Is Deprecated -20
Latest Podspec is declared to be deprecated
Lots of open issues -8
A project with a lot of open issues is generally abandoned. If it is a popular library, then it is usually offset by the popularity modifiers.
Interested in how it works? Read the Guide