openwrt/luci

LuCI - OpenWrt Configuration Interface

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 8th, 2026
Created on October 9th, 2014
Open Issues & Pull Requests: 460 (+0)
GitHub issues: Enabled
Number of forks: 2,931
Total Stargazers: 7,831 (+0)
Total Subscribers: 271 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.6 hours
Mean response time: 66.5 days
90th percentile: 66.1 days
Tracked items: 641

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 54% of tracked open issues have had no activity in three months. Only 6% of issues opened in the past year have been closed. Three people close 66% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 240
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 768 days
Stale 30+ days: 210
Stale 90+ days: 173

Recent activity

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

Top labels

  • request (11)
  • probably a bug (6)
  • help wanted (4)
  • release/18.06 (end-of-support) (3)
  • RFC (2)
  • feature (2)
  • more information needed (2)
  • release/19.07 (end-of-support) (2)

Detailed Description

LuCI is a web-based configuration interface for OpenWrt routers and embedded Linux systems.

The tool addresses the need for a user-friendly way to manage OpenWrt devices without direct command-line access. It provides a graphical interface built with JavaScript on the client side, using ucode and rpcd for server-side operations. The architecture separates presentation logic from system operations, allowing both web-based administration and programmatic access through documented APIs.

LuCI suits operators and administrators who need to configure OpenWrt systems through a browser rather than SSH or the command line. It works well for home networks, small business deployments, and any environment where centralized web-based management is preferred. The project includes client-side JavaScript APIs and generated API documentation for developers extending or integrating with the interface.

Development activity shows sustained engagement with the project. The team maintains a dedicated wiki for development and extension documentation, indicating investment in onboarding contributors. Translation management is handled through a dedicated platform rather than direct repository edits, suggesting organized community localization efforts. The project operates as an enabled-by-default feed within OpenWrt's package system, reflecting its role as core infrastructure rather than an optional add-on.