Ask HN: Criteria for judging JavaScript project?

I'm thinking about making a JS lib/framework comparison site, something like ruby-toolbox.com but for JS. And I need some objective/subjective criteria for comparing projects.

# Objective

I plan to use npmjs.com and github.com API to retrieve data and get some objective criteria. Apart from the apparent star/watcher/fork counts, NPM downloads, I come up with:

- Issue Open/Close ratio - Issue creation frequency - Commits frequency - Star increase frequency

Q: What are some of the objective and calculable criteria that you would use to judge a JS project?

# Subjective

I want to add user comment/rating for each project. I'm thinking about adding rating for:

- Code quality - Doc quality - Mail-list/Issue tracker responsiveness/helpfulness

Q: Are there other subjective criteria that you would find helpful for judging a project?