Add a community score(s).

[jamestalmage]

I'd love to see a score that told me a bit about the community on a project I was thinking of getting involved with. Specifically, I'd like to know:

1. How many people have made significant contributions (how big is the core team).
2. How many people have made any contribution (how big is the wider community that contributes, even a little).
3. How likely is it a PR from someone outside the core team will be merged.
4. How much bike-shedding (# of comments) and requested revisions are there for PR's from outsiders before merging. (How many hoops will I need to jump through to land a suggested change).

Items 1 & 2 are important for choosing a module to use in my project. 3 & 4 are more important for helping me decide if I want to get involved in the community.

[satazor]

I like the idea

1. This can be made with 1 additional request to GitHub per package (contributors request)
2. The same request made in 1. can be re-used (contributors request)
3. This can also be easily done by crossing the members of the 1 with the PR authors
4. This is tricky because I would have to get the comments for each PR which will greatly increase the number of requests per package, making the analisis pipeline slower and will also require a lot of GH access tokens

[satazor]

Also look at "Personalities" in https://npms.io/about

It's somewhat related but also different in some aspects.

[jamestalmage]

4. This is tricky

You wouldn't necessarily need to make that part of the overall score, and instead calculate on demand (add a "more info" dropdown with harder to query stuff like this). It's not info I would want often, but it would be invaluable on some occasions.