cockpit-project/cockpit

Cockpit is a web-based graphical interface for servers.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on May 11th, 2023
Created on November 1st, 2013
Open Issues & Pull Requests: 487 (+0)
Number of forks: 1,333
Total Stargazers: 14,965 (+0)
Total Subscribers: 188 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.6 hours
Mean response time: 177.7 days
90th percentile: 588.8 days
Tracked items: 1,316

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 64% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bot" is answered fastest, typically in about 3 hours, while "page:networking" waits about 8 months. 68% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 11% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 348
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 641 days
Stale 30+ days: 327
Stale 90+ days: 306

Recent activity

Opened in 7 days: 4
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 6

Top labels

  • bug (684)
  • enhancement (654)
  • nightly (607)
  • question (301)
  • good-first-issue (151)
  • needsdesign (86)
  • page:storage (82)
  • flake (80)

Detailed Description

Cockpit is a web-based graphical interface for Linux server administration that runs directly in a web browser. The project describes itself as "a sysadmin login session in a web browser" and provides an interactive server admin interface designed to be lightweight and easy to use. Rather than requiring administrators to work exclusively from the command line, Cockpit enables them to perform common system administration tasks through a graphical interface while maintaining full compatibility with terminal-based workflows.

The core functionality of Cockpit centers on making Linux systems more discoverable and accessible to system administrators. Through the web interface, users can start and manage containers, perform storage administration, configure network settings, inspect system logs, and manage user accounts. The interface supports both light and dark themes and includes dedicated sections for high-level system overview, account management, and network configuration. A key design principle is seamless integration with terminal workflows—services started through Cockpit can be stopped from the terminal, and errors occurring in the terminal appear in Cockpit's journal interface, allowing administrators to move fluidly between tools.

Cockpit's architecture enables multi-host management through SSH connectivity. Administrators can easily add other machines running Cockpit and jump between hosts without requiring separate login sessions. The project also provides a Flatpak application called Cockpit Client that includes SSH login support for connecting to remote Linux servers, expanding accessibility beyond traditional web browser deployments.

The repository shows substantial ongoing development and maintenance activity.

The codebase is primarily written in JavaScript and is available across numerous Linux distributions, typically packaged as "cockpit." Installation guidance and frequently asked questions are documented on the project website at cockpit-project.org. The project maintains multiple communication channels including a Matrix channel at #cockpit:fedoraproject.org and a development mailing list for community engagement.

Cockpit is licensed under multiple open-source licenses including LGPL-2.1 or later, GPL-3.0 or later, BSD-3-Clause, CC-BY-SA-3.0, and MIT, reflecting its use of diverse upstream components. The project maintains security documentation and manages translations through Weblate integration with the Fedora Project. Developer contributions are supported through comprehensive documentation including a HACKING.md file for quick environment setup and detailed contributor guidelines in the project wiki covering design proposals, testing procedures, and the overall contribution workflow.