libgit2 / libgit2/libgit2sharp
NuGet prefix reservation: LibGit2Sharp
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
There are a ridiculous number of packages in the nuget gallery that are named LibGit2Sharp. Some have version numbers greater than our own, a bunch include ssh binaries, and most have security vulnerabilities (but I repeat myself).
This is confusing as hell, and they're all using libgit2 trademarks and icons so certainly appear official. They're not.
I've contacted all the publishers and asked them to de-list their packages and mark them as deprecated. I'll follow up with a takedown request to nuget.org.
You can reserve a prefix in the NuGet gallery, so we could reserve the prefix. I think the LibGit2Sharp project should.
/cc @bording
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked NuGet ID prefix reservation application process and review the LibGit2Sharp packages described in the issue. Confirm the project’s ownership details and follow the reservation and takedown processes; done means the prefix request and related package actions have been completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100