folke/lazy.nvim

💤 A modern plugin manager for Neovim

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

Summary Information

Updated 55 minutes ago
Added to GitGenius on September 2nd, 2026
Created on November 20th, 2022
Open Issues & Pull Requests: 66 (+0)
GitHub issues: Enabled
Number of forks: 590
Total Stargazers: 21,538 (+1)
Total Subscribers: 59 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 hours
Mean response time: 9.3 days
90th percentile: 31.0 days
Tracked items: 183

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 4% of issues opened in the past year have been closed. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 255 days
Stale 30+ days: 2
Stale 90+ days: 1

Recent activity

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

Top labels

  • bug (126)
  • enhancement (74)
  • stale (60)
  • wontfix (18)
  • documentation (1)
  • invalid (1)
  • notstale (1)

Detailed Description

lazy.nvim is a modern plugin manager for Neovim that handles installation, loading, and management of plugins through a powerful UI.

The tool addresses the challenge of managing Neovim plugins efficiently while maintaining fast startup times. It achieves this through automatic caching and bytecode compilation of Lua modules, partial clones instead of shallow clones, and lazy-loading capabilities triggered by events, commands, filetypes, and key mappings. Plugins can be automatically installed before startup, and the tool handles dependency sequencing without requiring manual compilation. It supports async execution for improved performance and includes profiling tools to help optimize configuration.

Developers managing Neovim configurations should choose this tool if startup performance matters to them and they want to avoid manual plugin management overhead. It suits projects of any size where plugin organization and load-time optimization are priorities. The tool supports multiple configuration files, generates helptags from plugin README files, includes dev options for local plugin development, and maintains a lockfile for reproducible plugin states. It handles commit, branch, tag, version, and semantic versioning specifications, and can automatically check for updates with a statusline component to display pending update counts.

The project shows consistent maintenance with regular commits and active issue engagement. Development activity demonstrates responsiveness to user reports and feature requests. The codebase receives ongoing refinement and optimization work. The project maintains comprehensive documentation and tooling for users to diagnose and improve their configurations.