mljar/mercury

Impress your boss and turn a Jupyter notebook into a beautiful, shareable web app — no callbacks, no frontend, no rewrite.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 15th, 2026
Created on December 20th, 2021
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 291
Total Stargazers: 4,353 (+0)
Total Subscribers: 42 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.7 hours
Mean response time: 103.5 days
90th percentile: 461.2 days
Tracked items: 171

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. Work labelled "bug" is answered fastest, typically in about 3 hours, while "Mercury-Version-3" waits about 3 months. 95% of issues opened in the past year have since been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • bug (35)
  • help wanted (32)
  • enhancement (24)
  • Mercury-Version-3 (23)
  • good first issue (18)
  • documentation (5)
  • deployment (4)

Most active issues this week

Detailed Description

Mercury is a framework that transforms Jupyter notebooks into interactive web applications without requiring callbacks, frontend code, or notebook rewrites.

The problem Mercury solves is the gap between notebook-based data analysis and shareable web applications. Developers and data scientists often create analyses in Jupyter but struggle to share them as polished, interactive web apps. Mercury bridges this by letting you add simple Python decorators and components to your existing notebook code. The framework handles the conversion to a web interface automatically, preserving the notebook's logic while making it accessible through a browser without exposing the underlying code or requiring users to understand Python.

Mercury suits data scientists and analysts who want to share interactive analyses with non-technical stakeholders without learning web development. It works well for dashboards, data visualizations, and exploratory tools where the core logic already exists in a notebook. The tool is particularly valuable when you need to publish work quickly without restructuring your analysis code. Teams should consider Mercury when they want to avoid the overhead of building a separate web application while maintaining the flexibility of notebook-based development.

The project shows consistent development activity with regular updates addressing user feedback and expanding capabilities. The maintainers actively respond to issues and incorporate feature requests from the community. Development focuses on improving the ease of converting notebooks to web apps and expanding the range of interactive components available. The project maintains clear documentation and examples that help users get started quickly. There is ongoing work to enhance the visual appearance and customization options of generated applications.