nvim-treesitter/nvim-treesitter-context

Show code context

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 1 hour ago
Type:Plugin / ExtensionCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on October 19th, 2020
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 241
Total Stargazers: 3,229 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.7 hours
Mean response time: 26.4 days
90th percentile: 60.5 days
Tracked items: 72

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 363 days
Stale 30+ days: 16
Stale 90+ days: 14

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 (16)
  • enhancement (5)
  • accepted (2)
  • invalid (1)
  • not a bug (1)
  • question (1)
  • unable to reproduce (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

nvim-treesitter-context is a Neovim plugin that displays code context information.

The plugin addresses the problem of losing track of code structure when scrolling through large files or functions. It works by leveraging tree-sitter, the incremental parsing library, to understand the syntactic structure of code and display relevant context such as function names, class definitions, or block structures at the top of the viewport as you navigate.

The tool suits developers working with Neovim who frequently edit large files where understanding the surrounding code structure improves navigation and reduces cognitive load. It integrates with the tree-sitter ecosystem that Neovim users typically already have configured, making it a natural addition for those already using tree-sitter-based plugins.

The project shows active maintenance with regular commits addressing bug fixes and feature improvements. Pull requests receive timely review and integration. The codebase demonstrates responsiveness to user-reported issues with fixes deployed promptly.