Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Results are outdated. #101

Closed
antoniormrzz opened this issue Dec 30, 2020 · 3 comments
Closed

Results are outdated. #101

antoniormrzz opened this issue Dec 30, 2020 · 3 comments

Comments

@antoniormrzz
Copy link

This api returns 2 packages for me, I have 4. You can try with more users, namely sindresorhus has more than 1k but this api shows around 950.

@joebochill
Copy link

joebochill commented Dec 31, 2020

I'm seeing the same thing across a bunch of my packages. The data coming back appears to be several months old.

For example:

On NPMS search:
image

On NPM:
image

@dobladov
Copy link

dobladov commented Feb 26, 2021

I encountered the same problem for some popular packages:

webpack: https://api.npms.io/v2/package/webpack
Current version: 5.34.2
API version: 4.44.2

typescript: https://api.npms.io/v2/package/typescript
Current version: 4.2.2
API version: 3.4.3

AnalyzedAt value seems to be several months old, how often does the API update?

@satazor
Copy link
Member

satazor commented Oct 26, 2021

The issue had to do with some errors replicating from the npm registry.

I've created a script that enqueued outdated packages to be processed. The queue has 30k packages, and is slowly analyzing them. Should be done by tomorrow or the day next.

I will close this once it's done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants