You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
A page of every package on npm includes a stat which shows how many packages are dependent on it(dependents) and that number seems to be incorrect.
For example looking at the "base" package site (https://www.npmjs.com/package/base), its says there are 29 dependents but checking the actual list of dependents i can only count 28.
I came to the same conclusion with many other packages, doing my own aggregation on a replicated instance of the npm-registry.
There seems to be a problem with deleted and newly added packages not being taken in to account.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A page of every package on npm includes a stat which shows how many packages are dependent on it(dependents) and that number seems to be incorrect.
For example looking at the "base" package site (https://www.npmjs.com/package/base), its says there are 29 dependents but checking the actual list of dependents i can only count 28.
I came to the same conclusion with many other packages, doing my own aggregation on a replicated instance of the npm-registry.
There seems to be a problem with deleted and newly added packages not being taken in to account.
The text was updated successfully, but these errors were encountered: