Storytime 📢 Tell us how are you using Debricked's API?

  • 2 March 2023
  • 2 replies
  • 59 views

Userlevel 4

Greetings, portal ship members 🚀 It’s story time!

How are you harnessing the power of Debricked’s API to explore the vastness of the open source universe in your workflows?

We would love to hear your tales of triumph and feature you on our Community homepage! 

Share your knowledge in the comments below.


2 replies

I use selects api every time I check a github-site / package-manager site by using a small extension I wrote for my browser.
It checks the webpage you're currently visiting. If it's Github or a known package-manager site, then it tries to parse what repo / package it is. Then I send it to a select search endpoint and choose the best result, and show it in my extension.

e.g.
1. Check url of current tab
2. Extract package / repository name, if it's a known pm / repo (e.g. "github/owner/name" or "npm/name")
3. Then I send my findings to the following endpoint, with {extractedName} being the result from step 2.
> https://debricked.com/select/do-search?searchString={extractedName}&skipXResults=0

(for example, pypi/numpy - https://debricked.com/select/do-search?searchString=pypi/numpy&skipXResults=0 )
4. I extract relevant info such as each score and then show them in my extension.

Thus, it becomes very natural for me to just check every repository I visit and use that as extra information when picking/investigating open source, since it's available without extra hassle through my plugin.

 

Userlevel 4

Great tip @ProgHaj ! Thanks for sharing ✨

Reply