search

npms-io / npms-analyzer

The analyzer behind https://npms.io
MIT License
317 stars 38 forks source link

QUESTION: How often does https://npms.io analyze a package? #244

Closed edwardfxiao closed 4 years ago

edwardfxiao commented 5 years ago

How often does https://npms.io analyze a package?

I mean my package (for example https://npms.io/search?q=react-inputs-validation) has been updated to v3.4.12 whereas the score shows on https://npms.io still with v3.3.0.

And I do not understand why my package maintenance on npmjs.com suddenly dropped from 100% to 33%. Also quality and popularity dropped dramatically.

Cvmcosta commented 5 years ago

I knew i was not the only one, my package is already in the version 2.1.1, but in the npms search it still shows 1.0.33, and not in npms, but in npm my search results maintenance score has dropped from 100% to 33%

mlms13 commented 5 years ago

Has the analyzer just stopped running? I published a package about 3 weeks ago and it still hasn't been picked up.

satazor commented 5 years ago

There’s a problem in the couchdb registry we are replicating from. The analyzer is working correctly but we aren’t receiving any updates. I’ve tried to reach out to npm via twitter but got no response: https://twitter.com/npms_io/status/1161303398446227456?s=21

I will have to try to reach them via email in a more formal way. @isaacs can anyone on npm’s side help with this?

theophilusx commented 5 years ago

Is there any update on this? Details on my package are way out of date, showing wrong version number and incorrect data for quality and maintenance. There has been 5 releases since the last update by npms.io

jimmylewis commented 5 years ago

@satazor any updates? Were you able to get through to NPM support? This is also adversely affecting package version completion scenarios in Visual Studio and VS Code.

satazor commented 4 years ago

I’ve spoken with the search DRI of npm and there was a miss configuration that was fixed. Some packages might take longer to recover than others, but you should soon see them updated.

edwardfxiao commented 4 years ago

@satazor Hi, I just wanted to ask, the scores on https://npms.io/ are correct currently, however, it is still wrong on https://www.npmjs.com/.

I know its probably an issue with npm side, but could you talk to them about it?

theophilusx commented 4 years ago

Confirm that I'm seeing the same thing. My package data on npms.io is now up-to-date, but the data on npmjs.com is still old/outdated. I did log an issue with npmjs.com, but the reply I received completely missed the issue. I sent a follow up reply, but got no response.

Borewit commented 4 years ago

Regarding wrong scores on npmjs.com, please vote on the issue I created: npm.community#10664

theophilusx commented 4 years ago

done.

On Wed, 30 Oct 2019 at 17:55, Borewit notifications@github.com wrote:

Regarding wrong scores on npmjs.com https://www.npmjs.com/, please vote on the issue I created: npm.community#10664 https://npm.community/t/npmjs-com-scores-quality-popularity-maintenance-seems-to-be-wrong/10664

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/npms-io/npms-analyzer/issues/244?email_source=notifications&email_token=AAMFIKNSQFQMJXS5LZONNILQREVWVA5CNFSM4ITMRXDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECTDG2Y#issuecomment-547763051, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMFIKJ3DEL75OIW7R2O3TLQREVWVANCNFSM4ITMRXDA .

-- regards,

Tim

-- Tim Cross

Borewit commented 4 years ago

I am keeping track of this issue, NPM seems not very keen on giving any response.

If someone could help me (us) to bring this under their attention, that would be great.

theophilusx commented 4 years ago

I received the following response from npmjs.com regarding the outdated package statistics issue

Ahmad Nassri (npm)

Dec 27, 13:32 PST

Hey Tim,

apologies for the frustration here, we've been dealing with heavy rate limiting by GitHub when calling their APIs to enquirer about package data (we get the data that powers the quality ratings for packages from GH directly).

npms.io is not affiliated with npm, inc. we do not share any servers or data with them or from them, it is entirely 3rd party run, and honestly quite puzzling why they are not getting rate-limited by github as we do.

thank you for your patience.

On Thu, 7 Nov 2019 at 19:34, Borewit notifications@github.com wrote:

I am keeping track of this issue https://github.com/Borewit/music-metadata/issues/293, NPM seems not very keen on giving any response.

If someone could help me (us) to bring this under their attention, that would be great.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/npms-io/npms-analyzer/issues/244?email_source=notifications&email_token=AAMFIKJWV2QLXLY7QJC7TYDQSPHIHA5CNFSM4ITMRXDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDLUALY#issuecomment-550977583, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMFIKPCFZAN4WH4SJMM5JTQSPHIHANCNFSM4ITMRXDA .

-- regards,

Tim

-- Tim Cross

satazor commented 4 years ago

We are rate limited by GitHub as well, but we have a total of 10 GitHub access tokens that were given by people close to the authors. Those are sufficient to keep a high concurrency for now.