neovim/nvim-lspconfig

Quickstart configs for Nvim LSP

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 minute ago
Added to GitGenius on September 4th, 2026
Created on November 13th, 2019
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 2,489
Total Stargazers: 13,929 (+0)
Total Subscribers: 80 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.5 hours
Mean response time: 15.7 days
90th percentile: 10.7 days
Tracked items: 405

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 67% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Only 8% of issues opened in the past year have been closed. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 428 days
Stale 30+ days: 22
Stale 90+ days: 19

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (314)
  • enhancement (43)
  • question (30)
  • documentation (9)
  • ci (2)
  • invalid (2)
  • dependencies (1)
  • upstream (1)

Most active issues this week

Detailed Description

nvim-lspconfig is a collection of language server protocol configurations for Neovim's built-in LSP client.

The tool solves the problem of connecting Neovim to language servers by providing pre-configured server definitions that handle the details of launching and communicating with each language server. Rather than requiring users to manually configure every aspect of each server, nvim-lspconfig supplies ready-to-use configurations that specify how to start servers, detect project root directories, and map file types to the appropriate language server. Users enable servers through Neovim's native LSP configuration system and the tool automatically merges its server-specific settings with any local customizations.

Developers should adopt this tool if they use Neovim 0.11 or later and want language server support without manual configuration overhead. It suits any project where you have language servers installed and want Neovim to provide diagnostics, completion, and other LSP features. The tool is undergoing a transition: the legacy require-based API is deprecated in favor of Neovim's native vim.lsp.config system, so new users should use vim.lsp.enable and vim.lsp.config rather than the older setup methods. The README emphasizes that these configurations are community-maintained best-effort work, with bug reports about Neovim's core LSP functionality directed to Neovim itself rather than this repository.

Development activity shows that the project maintains a large collection of server configurations across many languages and tools, with community contributions handling most server-specific work. The codebase is actively managed to align with Neovim's evolving LSP APIs, including the significant migration away from the legacy framework toward native configuration methods. The project clearly delineates responsibility boundaries, routing core LSP bugs upstream to Neovim while keeping this repository focused on configuration data and server-specific setup details.