itchyny/lightline.vim

A light and configurable statusline/tabline plugin for Vim

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 9th, 2026
Created on August 21st, 2013
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 316
Total Stargazers: 6,871 (+0)
Total Subscribers: 71 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 hours
Mean response time: 25.7 hours
90th percentile: 23.6 hours
Tracked items: 17

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • configuration (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

lightline.vim is a statusline and tabline plugin for Vim that prioritizes minimal overhead while remaining highly configurable.

The plugin addresses the need for a lightweight statusline solution that avoids the complexity and dependencies of heavier alternatives. It achieves this through a small core implementation that handles essential statusline functionality without relying on other plugins' internals. Users configure their statusline by defining components and arranging them through simple configuration in their vimrc, rather than the plugin making assumptions about what other plugins should provide.

Developers should choose this tool if they want a fast, dependency-free statusline with full control over its appearance and behavior. It suits projects where minimalism matters and where users prefer explicit configuration over convention. The README positions it against vim-powerline, which is deprecated; powerline, which the author found difficult to configure; and vim-airline, which the author felt delegated too much responsibility to other plugins rather than letting users decide their own setup.

The project maintains active engagement with its user base through issue responses and incorporates user-contributed improvements. Development follows a pattern of incremental refinement, with updates addressing both bug reports and feature requests from the community. The codebase remains tightly scoped, with changes focused on core functionality and configuration flexibility rather than feature expansion.