max-mapper/menubar

➖ high level way to create menubar desktop applications with electron

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 9th, 2026
Created on March 23rd, 2015
Open Issues & Pull Requests: 76 (+0)
GitHub issues: Enabled
Number of forks: 363
Total Stargazers: 6,781 (+0)
Total Subscribers: 54 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 153.1 days
Mean response time: 421.7 days
90th percentile: 1322.7 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,588 days
Stale 30+ days: 12
Stale 90+ days: 5

Recent activity

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

Top labels

  • good first issue (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Menubar is a high-level framework for creating menubar desktop applications with Electron.

The tool solves the problem of boilerplate setup when building menubar-style applications—those that live in the system tray or menu bar rather than as traditional windowed applications. It abstracts away the complexity of configuring Electron's app, window, and tray components by requiring only that you point it at an HTML file. The framework handles window positioning, tray icon management, and lifecycle events automatically, exposing the underlying Electron instances for cases where direct access is needed.

Menubar suits developers building lightweight system utilities, status monitors, or quick-access tools that should integrate with the desktop environment rather than appear as standalone windows. The tool is particularly valuable for projects prioritizing minimal bundle size and simplicity over extensive customization. It works across macOS, Windows, and Linux, though platform-specific behavior varies. The project explicitly states it has only one dependency and one peer dependency, keeping the dependency tree lean.

Development activity shows consistent maintenance with passing automated tests and active dependency monitoring. The project maintains a small, focused codebase reflected in its minified and gzipped size, suggesting the maintainers prioritize keeping the tool lightweight and avoiding feature creep.