Surfacing GitHub Usage for packages on NuGet.org

Avatar

Mohamed Riad

There are several criteria you can use today to evaluate NuGet packages. We received feedback that you would like even more information to help choose the right packages. We’re excited to introduce GitHub Usage on nuget.org, which allows you to explore top GitHub repositories that depend on the package you are looking at.

GitHub Usage section

Why surface GitHub Usage?

Part of determining a package’s trust and popularity is to know if the package is being used, who is using it, and how are they using it.

A NuGet package depended by a popular GitHub project is more likely to be trustworthy than a package used by a less known repository.

You can use GitHub’s star system as an indication of a repository’s popularity, which you can use as a criterion to evaluate a NuGet package. To set a quality baseline metric, we established that repositories with at least 100 stars are popular enough to be indexed by our service.

Another common feedback we hear is that in some cases it is difficult to find good examples of how to use a package. We have tried to address this by displaying a short description of the GitHub repositories and providing links to access them, which should help in finding good examples of how a particular NuGet package is used.

What’s next?

In the future, we plan to extend this feature to show interdependencies between NuGet packages. You can track the status of that feature using this GitHub issue.

We want to hear your feedback!

We want NuGet to meet the evolving needs of our community. Post a comment or use the GitHub issue tracking this experience to provide feedback, or ask questions. You can also reach out to us on twitter – mention @nuget in your tweets.

Avatar
Mohamed Riad Gahlouz

Software Engineer Intern, NuGet Team

Follow Mohamed Riad   

3 comments

Comments are closed.

  • Avatar
    Sandy Armstrong

    This is great! If I could make one suggestion: change the wording in the “info” sidebar from “Dependent repositories (223+)” to “Github Usage: 223+ repositories”.
    Even for native speakers, I feel pretty confident that a lot of people are going to read “Dependent repositories” and think it means how many dependencies the nuget package has, which is exactly the opposite of what you want to communicate, and may scare people away.
    Sticking with “Github usage” is more consistent with the other new section on the page, too.

    • Avatar
      Loïc Sharma

      I can see how this may be confusing, thank you for the feedback! I agree that the ideal wording would be consistent with the GitHub Usage section’s title. In the future, we will also show which NuGet packages depend on the current package, so we’ll be sure to make these labels as clear as possible. 

  • Barkha Verma
    Barkha Verma

    I feel pretty confident that a lot of people are going to read “Dependent repositories” and think it means how many dependencies the nuget package has, which is exactly the opposite of what you want to communicate.
    skype push to talk