folke/snacks.nvim

🍿 A collection of QoL plugins for Neovim

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 8th, 2026
Created on November 2nd, 2024
Open Issues & Pull Requests: 141 (+0)
GitHub issues: Enabled
Number of forks: 496
Total Stargazers: 8,078 (+1)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 hours
Mean response time: 6.6 days
90th percentile: 26.7 days
Tracked items: 1,265

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 7% 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: 29
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 90 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (842)
  • enhancement (512)
  • stale (319)
  • wontfix (128)
  • prio:high (2)
  • cant fix (1)
  • documentation (1)
  • notstale (1)

Detailed Description

snacks.nvim is a collection of quality-of-life plugins for Neovim that bundles multiple small utilities into a single package.

The project addresses the friction of managing many small Neovim plugins by consolidating commonly needed utilities into one cohesive collection. Rather than installing separate plugins for each minor enhancement, users get a bundled set of tools designed to work together. The approach groups related functionality while keeping individual modules lightweight and optional, so users can enable only what they need.

Developers should choose this tool if they want to reduce plugin management overhead while gaining quick access to common QoL improvements. It suits Neovim users who prefer a curated, integrated experience over assembling many single-purpose plugins. The project is particularly valuable for those who want sensible defaults without the configuration burden of wiring together multiple separate packages.

The project shows consistent development activity with regular commits addressing bug fixes and feature additions. Work spans across multiple areas of the codebase rather than concentrating on a single component. The maintainer actively responds to issues and incorporates user feedback into updates. Documentation receives ongoing attention alongside code changes, keeping the README and examples current with the tool's capabilities.