The npms-analyzer analyzes the npm ecosystem, collecting info, evaluating and scoring each package.
This project offers all its functionality through a CLI.
Note that you must setup the project before using the CLI. The most important commands will be described below. To discover the other ones run $ npms-analyzer -h.
The observe command starts observing changes that occur in the npm registry as well as packages that were not analyzed for a while. Each reported package will be pushed into a queue to be processed by the queue consumers.
$ npms-analyzer observe --log-level debug | pinoFor more information about the command, run $ npms-analyzer observe -h
The consume command starts consuming the queue, running the analysis process for each queued package.
$ npms-analyzer consume --log-level debug --concurrency 5 | pinoFor more information about the command, run $ npms-analyzer consume -h
The scoring command, continuously iterates over the analysis results and calculates a score for all the npm packages, storing its result in elasticsearch.
$ npms-analyzer scoringFor more information about the command, run $ npms-analyzer scoring -h
There's a separate document that explains the architecture, you may read it here.
There's a separate document that explains the setup procedure, you may read it here.
There's a separate document that explains the deployment procedure, you may read it here.
Before running the tests, you must have read through the setup guide.
$ npm test
$ npm test-cov # to get coverage report