jupyter/notebook

Jupyter Interactive Notebook

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 2 hours ago
Added to GitGenius on January 5th, 2025
Created on April 9th, 2015
Open Issues & Pull Requests: 1,891 (+0)
GitHub issues: Enabled
Number of forks: 5,789
Total Stargazers: 13,431 (+0)
Total Subscribers: 322 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.7 days
Mean response time: 436.7 days
90th percentile: 1905.0 days
Tracked items: 480

Maintainer activity

5 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 4% of issues opened in the past year have never received a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "status:Needs Triage" is answered fastest, typically in about 16 hours, while "documentation" waits about 8 days. 62% of issues opened in the past year have been closed, leaving a working backlog. Three people close 68% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,217
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 2,455 days
Stale 30+ days: 1,210
Stale 90+ days: 1,200

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 5

Top labels

  • status:resolved-locked (1,211)
  • bug (442)
  • enhancement (251)
  • status:Needs Triage (221)
  • status:Needs Info (133)
  • tag:Accessibility (97)
  • question (74)
  • documentation (69)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The Jupyter Notebook repository is a web-based interactive computing environment that serves as the language-agnostic successor to IPython Notebook. Following the Big Split of the IPython codebase in 2015, Jupyter Notebook evolved into a standalone project designed to support computation across multiple programming languages through pluggable kernel architecture. The repository maintains the core notebook application while language-specific kernels are developed in separate repositories, allowing the project to scale across diverse computing ecosystems.

The project currently maintains two major versions in active development. Notebook v7 represents a significant architectural shift, built on JupyterLab components for the frontend and Jupyter Server for the Python backend. This modernization enables better integration with the broader JupyterLab ecosystem and provides a foundation for future development. Classic Notebook v6, the previous major version, is maintained on the 6.5.x branch with focus limited to maintenance and security fixes, with its frontend assets managed through the nbclassic dependency. Notebook v5 is no longer maintained, and users are encouraged to upgrade to either v6 or v7.

The repository is classified across a comprehensive range of domains reflecting its broad utility: notebook interfaces, Jupyter ecosystem components, interactive computing, code execution, visualization, data analysis, scientific computing, machine learning, educational tools, web-based IDE functionality, and support for multiple programming languages. This classification underscores the notebook's role as a foundational tool spanning data science, research, education, and collaborative development workflows.

The repository's documentation is maintained on ReadTheDocs, with installation and usage guidance available through the official Jupyter documentation portal. Development contributions are governed by the Jupyter Community Guides and Code of Conduct, with detailed contribution procedures documented in the CONTRIBUTING.md file.