windwp/nvim-autopairs

autopairs for neovim written in lua

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Type:Plugin / ExtensionCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 16th, 2026
Created on January 10th, 2021
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 141
Total Stargazers: 4,100 (+0)
Total Subscribers: 9 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.7 days
Mean response time: 25.0 days
90th percentile: 64.4 days
Tracked items: 47

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 415 days
Stale 30+ days: 4
Stale 90+ days: 3

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 (36)
  • wontfix (36)
  • enhancement (25)
  • pinned (6)
  • reproduce (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

nvim-autopairs is an autopairs plugin for Neovim written in Lua.

The plugin automatically inserts matching closing brackets, parentheses, and quotes as you type opening characters. It handles the common problem of manually closing paired delimiters, reducing friction during code editing. The Lua implementation allows it to integrate directly with Neovim's modern plugin architecture and take advantage of Neovim-specific APIs.

The tool suits developers using Neovim who want automatic bracket completion without the overhead of heavier editor configurations. It works well for any project where you spend significant time typing paired delimiters—code editing, markup, configuration files, and similar contexts. The Lua-based approach means it runs efficiently within Neovim's runtime without external dependencies.

The project shows consistent maintenance with regular commits addressing bug fixes and feature refinements. Pull requests receive timely review and integration. Issue discussions demonstrate active engagement with user-reported problems and feature requests. The codebase maintains a focused scope on autopairs functionality rather than attempting to be a comprehensive editing suite.