Badge request: dependents of a npm package

[sindresorhus]

Would be nice to have a badge to show off how many npm packages depend on my package. For example, the 1717 Dependents number at https://www.npmjs.com/package/got.

You could either:

• Use the API. Example: https://github.com/chrisdickinson/npm-get-dependents
• Scrape. Example: https://github.com/astur/check-npm-dependents

[paulmelnikow]

The API doesn't match the number on the npm site. See chrisdickinson/npm-get-dependents#3. I confirmed that through my own experimentation with the endpoint it uses on the legacy npm registry mirror. (https://skimdb.npmjs.com/registry/_design/app/_view/dependedUpon)

Scraping npmjs is a nice solution, and more server capacity would enable that. See my proposal at #1742 (comment) and some actionable work in #1848.

I have an implementation using Libraries.io, which we've used elsewhere. (#1895) That API is on the slow side, but it works, and may be an acceptable option for the time being.

[hiteshpr]

I can work on this.

[paulmelnikow]

I just learned about npms! We could base this on their API.

[ainthek]

I just learned about npms! We could base this on their API.
I had a quick look at the API on npmjs, but is there any way to get dependents ? I did not find it. Thanx

[calebcartwright]

I had a quick look at the API on npmjs, but is there any way to get dependents ? I did not find it.

Though it's not explicitly called out in the npms API docs, the API response does include a value for dependents count in collected.npm.dependentsCount

https://api.npms.io/v2/package/got

{ 
  "analyzedAt":"2019-10-19T11:32:46.782Z",
  "collected":{ 
    "metadata":{ .. },
    "npm":{ 
      "downloads":[ .. ],
      "dependentsCount":2349,
      "starsCount":124
    },
    "github":{ .. },
    "source":{ .. }
  },
  "evaluation":{ .. },
  "score":{ .. }
}

However, I think the same issue exists here relative to the counts being off. The registry shows (at the time of this post) 2,844 dependents for got whereas the API response from npms shows 2,349

[calebcartwright]

Probably worth keeping tabs on npms-io/npms#37 over in the npms repo to see if there's an explanation for the descrepancy