node-red/node-red-dashboard

A dashboard UI for Node-RED

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

node-red/node-red-dashboard has 1k+ stars and 450+ forks on GitHub, is written in HTML, and was last pushed on Aug 7, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on May 5th, 2016
Open Issues & Pull Requests: 93 (+0)
GitHub issues: Enabled
Number of forks: 479
Total Stargazers: 1,407 (+0)
Total Subscribers: 77 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.3 hours
Mean response time: 203.7 days
90th percentile: 2.3 days
Tracked items: 10

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: 675 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Node-red-dashboard is a dashboard UI module for Node-RED that provides a set of nodes to quickly create a live data dashboard.

The tool solves the problem of building interactive data visualization interfaces within Node-RED workflows. It works by offering a collection of dashboard nodes that can be wired into flows to display and control data in real time. The dashboard is accessed through a web interface and uses a grid-based layout system where groups and widgets are positioned automatically to fill space efficiently from top-left to bottom-right.

Developers should be aware that this project is deprecated as of mid-2024 and is considered to be on life support. The README explicitly recommends that users consider alternative solutions for production use, naming Flowfuse Dashboard as the most direct replacement and UIBUILDER as another option. The tool remains installable for those who need it, but new projects should evaluate these alternatives before committing to adoption.

Development activity on the project is minimal. The codebase receives only small patches on a best-effort basis with no major feature work underway. The project remains available for installation and use but should not be expected to evolve or receive proactive maintenance.