My node package's quality score went from 99% to 65% on an update

Asked Apr 12 '20 at 23:20

Active Apr 13 '20 at 00:06

Viewed 250 times

The goal of the update was to add the files property to the package.json to lead to a smaller download. Nothing else but the readme changed.

Code coverage is still 100%. Issues are closed. There are no outstanding PRs.

I used to have the second or third spot on NPM for all my relevant search terms. Now I'm not on the front page.

When I look at npms.io, the score is for a version from two months ago. I don't know how to get it updated. That version is quality 99.99%

How do I diagnose what is downgrading my quality score?

Edit: oh, wow. I removed the files section and the quality went back up to 95.

Either the presence of a files section broke it, or the quality is somehow dependent on a file I was excluding

edited Apr 13 '20 at 00:06

asked Apr 12 '20 at 23:20

John Haugeland

Does this answer your question? [How npmjs.com calculates the code quality](https://stackoverflow.com/questions/49866588/how-npmjs-com-calculates-the-code-quality) – Joseph Sible-Reinstate Monica Apr 12 '20 at 23:26
No, it does not. NPMjs hasn't used npms.io for a long time, and as I said, I did check it already; it's a month out of date – John Haugeland Apr 12 '20 at 23:34

0 Answers0