Andrew Nesbitt

And at the bottom end of the chart: | Name | SourceRank 1 | SourceRank 2 | | ------------- | ------------- |-------------| | gem_plugin | 2 | 43/100 | |...

Taking [text-format](https://rubygems.org/gems/text-format) as a low scoring project as an example of things in possibly change: ```json { "overall_score": 36, "popularity": { "score": 0.0, "dependent_projects": 0.0, "dependent_repositories": 0, "stars": 0, "forks":...

Updated the calculator to not punish projects that aren't on GitHub, here's the new breakdown for `text-format`, with an increased score from 36 to 42: ```json { "overall_score": 42, "popularity":...

Other related areas to think about when it comes to different levels of support for package manager features we have: - [x] if we don't support parsing `dependencies` for that...

- [x] I wonder if the `outdated_dependencies_score` should be a percentage based on the number of dependencies it has that are outdated

Probably also want to skip the `dependent_*` popularity scores if we don't have the support for it in that ecosystem, just wondering how many ecosystems that will affect: | Name...

Three of the double false package managers in the table are editor plugins and don't really do dependencies: Alcatraz, Emacs, Sublime The others are either smaller, we don't have any...

Atom is also a little weird here because it depends on npm modules and uses package.json, so doesn't really have either, but is flagged as having both, basically all the...

@e-beach thanks!

Moving this to the [Backlog](https://github.com/librariesio/libraries.io/blob/master/Backlog.md) as we'd still like to implement it but can't see that happening in the near future.