purpleidea/mgmt

Next generation distributed, event-driven, parallel config management!

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 16th, 2026
Created on September 25th, 2015
Open Issues & Pull Requests: 89 (+0)
GitHub issues: Enabled
Number of forks: 354
Total Stargazers: 4,319 (+0)
Total Subscribers: 92 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.9 hours
Mean response time: 362.2 days
90th percentile: 1804.6 days
Tracked items: 150

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 12% of issues opened in the past year have never received a reply. 41% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bug" is answered fastest, typically in about 12 hours, while "mgmtlove" waits about 5 months. 72% of issues opened in the past year have been closed, leaving a working backlog. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 29
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 950 days
Stale 30+ days: 23
Stale 90+ days: 20

Recent activity

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

Top labels

  • help wanted (44)
  • mgmtlove (29)
  • good first issue (19)
  • bug (12)
  • confirmed (7)
  • hacker (7)
  • design (3)
  • enhancement (2)

Detailed Description

mgmt is a distributed configuration management tool that executes infrastructure automation through event-driven, parallel processing across multiple machines.

The tool addresses the limitations of traditional sequential configuration management by treating infrastructure state as a directed acyclic graph where resources and their dependencies are modeled as nodes and edges. Rather than applying changes serially, mgmt evaluates this graph continuously and executes changes in parallel whenever possible, triggering updates reactively when state diverges from the desired configuration. The event-driven architecture means the system responds immediately to changes rather than waiting for scheduled runs, and distributed execution allows coordination across multiple nodes without a central bottleneck.

Teams should consider mgmt if they operate infrastructure at scale where parallelization and responsiveness matter, or if they want to move beyond the polling-based model of traditional configuration management. The tool suits projects where infrastructure topology is complex enough to benefit from explicit graph representation and where teams can adopt a Go-based system. The README does not position the tool against specific alternatives, so direct comparisons to other configuration management systems are not available from the project documentation.

Development on the project shows consistent activity with regular commits addressing both new features and maintenance. The codebase demonstrates active refinement of core functionality and ongoing attention to the distributed systems aspects that define the tool's architecture. Work spans infrastructure improvements and feature development, indicating the project is neither in early experimental stages nor in maintenance-only mode.