nvimtools/none-ls.nvim

null-ls.nvim reloaded / Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Plugin / ExtensionCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on August 30th, 2023
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 121
Total Stargazers: 3,263 (+0)
Total Subscribers: 6 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.7 hours
Mean response time: 54.3 days
90th percentile: 158.8 days
Tracked items: 51

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 398 days
Stale 30+ days: 7
Stale 90+ days: 7

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 (23)
  • enhancement (17)
  • help wanted (5)
  • external (4)
  • duplicate (2)
  • documentation (1)
  • invalid (1)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

none-ls.nvim is a Neovim plugin that acts as a language server to inject LSP diagnostics, code actions, and more via Lua.

Neovim's LSP client lacks a native mechanism for non-LSP sources to hook into LSP features, unlike VS Code and coc.nvim. none-ls bridges this gap by allowing pure Lua sources to provide diagnostics, code actions, formatting, hover information, and completion through the LSP protocol. The tool includes built-in sources for each of these features and provides helpers to streamline the process of spawning command-line tools and transforming their output into LSP-friendly formats. This approach reduces boilerplate and improves performance by eliminating the need for external language server processes.

The tool suits developers who want to extend Neovim's LSP capabilities with custom or community-maintained sources without running separate server processes. It works well for those already using Neovim's LSP ecosystem alongside plugins like telescope.nvim and trouble.nvim. The project is in beta status and is developed and tested against the latest stable version of Neovim, with best-effort support for development builds.

The project is community-maintained following the original author's transition away, with an open contribution model where pull requests can make contributors collaborators. The codebase maintains full API compatibility with its predecessor, requiring only a package manager source change for migration. Development follows a collaborative review process where pull requests require review from another collaborator before merging.