2 ms·
NPM (nodejs package manager) has started doing that, revealing three combined metrics for each package in the search results. It assesses every package by popul
by josephg 8y ago
NPM (nodejs package manager) has started doing that, revealing three combined metrics for each package in the search results. It assesses every package by popularity (number of downloads), quality (a dozen or so small heuristics about how carefully the project has been created) and maintenance (whether the project is actively maintained, keeps its dependancies up to date and if it and has more closed issues than open issues on github). The idea is that when you search for a package, you can see at a glance the relative quality and popularity of the modules you're choosing between.
Its not perfect - there's no way to tell if the packages under consideration are written in a consistent style or if they have thorough unit tests, but its a clever idea. And by rating packages on these metrics they encourage a reasonable set of best practices (write a readme and a changelog, use whitelists / blacklists, close issues on github, etc). The full list of metrics is here:
https://itnext.io/increasing-an-npm-packages-search-score-fb557f859300 https://itnext.io/increasing-an-npm-packages-search-score-fb...