Consider removing the nodegit link

Open
#117 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js
Domain
documentation

Research direction

Search the website content for the nodegit link and inspect the surrounding page or source file. Remove the outdated link, then verify that the published site no longer directs Node.js developers to nodegit.

Written by the indexing model from the issue text.

Description

libgit2.org lists nodegit as a Node.js binding of libgit2. However, the last stable release of nodegit is from 2020, there are no prebuilt binaries for any supported Node.js version anymore (only Node 16), and it depends on the long-deprecated "request" library that has security vulnerabilities. There are several issues asking about the project state without replies from the maintainers.

Developers looking for a library to use Git in Node.js will likely just get frustrated when they start with using Node.js.

Dominant language
CSS
Stars
116
Forks
67
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libgit2/www.libgit2.org

All issues in libgit2/www.libgit2.org

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.