npm-score-dummy
v1.2.5
Published
npm score dummy
Downloads
5
Readme
npm-score-dummy
Why do the newly created empty packages get 100% quality score, while the mature and useful packages don't?
Unfortunately, npm does not publish the scoring algorithm. Have to experiment...
Release log
| ver | p | q | m | notes | | :------- | -: | -: | -: | - | | 1.0.0 | 0 | 47 | 0 | Added package.json and index.js | 1.0.1 | 0 | 50 | 0 | Added tags | 1.0.2 | 0 | 60 | 0 | Added two npm badges | 1.0.3 | 0 | 60 | 0 | Just updated the version number | 1.0.4 | 0 | 62 | 0 | Added eslint | 1.0.5 | 0 | 62 | 33 | Added test | 1.0.6 | 1 | 62 | 33 | Added LICENSE.md | 1.0.7 | 1 | 62 | 33 | Added .gitignore and .gitattributes | 1.0.8 | 1 | 62 | 33 | Added .npmignore | 1.0.9 | 1 | 62 | 33 | Added GitHub Actions badge | 1.1.0 | 1 | 62 | 33 | Enabled GitHub action | 1.1.1 | 1 | 62 | 33 | Added dependency | 1.1.2 | 1 | 62 | 33 | Just updated the version number | 1.1.3 | 1 | 62 | 33 | Added RunKit badge | 1.1.4 | 1 | 89 | 33 | Added mocha test | 1.1.5 | 1 | 89 | 33 | Moved test to subdirectory | 1.1.6 | 1 | 89 | 33 | Added nyc | 1.1.7 | 1 | 89 | 33 | Enabled coverage | 1.1.8 | 1 | 89 | 33 | Added coverage command | 1.1.9 | 1 | 62 | 33 | Updated .npmignore | 1.2.0 | 1 | 89 | 33 | Fixed .npmignore | 1.2.1 | 1 | 89 | 33 | Opened GitHub issue | 1.2.2 | 1 | 89 | 33 | Closed GitHub issue | 1.2.3 | 1 | 90 | 33 | Custom homepage link | 1.2.4 | 1 | 90 | 33 | Unignored .eslintrc.js | 1.2.5 | 1 | 90 | 33 | Reverted previous change