Skip to content

Instantly share code, notes, and snippets.

@heapwolf
Last active December 11, 2015 10:38
Show Gist options
  • Save heapwolf/4587747 to your computer and use it in GitHub Desktop.
Save heapwolf/4587747 to your computer and use it in GitHub Desktop.
general heuristics for ranking package quality

Health

Has CI

Tests pass

Total number of breaking commits

Number of dependencies

Average age of issue

Frequency of issues fixed

Average response time of issues fixed to bugs filed

Last commit

Frequency of releases

Popularity

Number of dependent modules

Number of total downloads

Frequency of downloads

Frequency of commits

Number of contributors

Quality

Is well documented.

A markdown based README can be parsed to find headers corresponding to the man pages spec or else if there is no pattern match, a set of basic rules.

Number of Major releases

Reaching version 1.0 for node modules represents a significant milestone in stability.

Number of npm stars

When someone runs npm star <module-name> they are making a public statement about their appreciation for it.

Number of github stars

When someone stars a github repo they are making a public statement about their interest in it.

@rajaraodv
Copy link

+1 this will help a lot

@clintandrewhall
Copy link

I'd love to see tests / test coverage as part of quality, however best expressed?

@heapwolf
Copy link
Author

@brucecoddington
Copy link

+1 This would be excellent for any package management

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment