What I Wanted to Do
I published a new version of my package to NPM. I replaced TravisCI with GitHub Actions. I expected my maintenance score to stay at 100%, and my quality score to stay the same.
What Happened Instead
My maintenance score, like most packages with recently published versions, dropped to 33% for some odd reason. My quality score lowered to 64%, most likely because the npms.io analyzer doesn’t support GitHub Actions yet (for some reason it doesn’t show up in repo statuses).
See my repo. If you have a repo with CI and recent enough commits, you would expect decent maintenance and quality scores. The quality score isn’t really a bug, just a missing feature. If you publish a package, even with recent enough commits, you get a maintenance score of 33% for some reason. Even well-maintained packages like React have maintenance scores of 33% right now.
The main problem here is maintenance scores randomly dropping to 33%. The problem with the analyzer not supporting GitHub Actions is hard to address, because the project hasn’t been committed to in 5 months and a PR hasn’t been accepted in 7 months.
Does anybody have an idea about how I can help with this at all?