Next generation distributed, event-driven, parallel config management!
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 7%
Response Time: 5h
First Timer Success: -
purpleidea/mgmt has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in purpleidea/mgmt respond to incoming external pull requests in approximately 4.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 46.2 places purpleidea/mgmt in the B tier.
The external contributor pull request merge rate for purpleidea/mgmt is 7.4%, based on public PR activity from non-core contributors.
purpleidea/mgmt currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in purpleidea/mgmt. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/purpleidea/mgmt?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (9% approval). Large PRs (>500 lines) take ~22 hours (15% approval). Keep your diff compact for rapid review.
coreos/go-systemd#229 (comment) is the main blocker. This may be related: coreos/go-systemd#507 Amazingly, the well-known library is secretly polling :/
In our lexer (in lexer.nex) we drop all the comments found. This made it easier to write the parser, and is common practice, but we actually need to parse them if we want to eventually have an mgmt fmt type tool that prints out the parsed AST. As a result, we'd like to add them in wherever they are needed to parser.y. If you are a yacc or goyacc expert, we'd appreciate the help! If you can do this in a minimally invasive way, such that it doesn't make the whole thing wholly unreadable, that would be lovely. This will need a bunch of new tests in TestAstFunc1/ or TestAstFunc2/ or perhaps it's even better to have a TestAstFuncX that is specialized for looking at parsed AST shape? Once this is done, we can "print" out the AST to get back the original source (or our formatted version of it of course!) A future step is removing the required trailing comma on single line lists and similar...
We have a pretty good test facility for testing the language and the function engine in TestAstFunc2 (and similar). We'd like to build something similarly good for testing resources and resource graphs. It will be challenging to have something that makes it both easy to write tests succinctly, but also which can run hundreds of tests of many resources each, and which doesn't cause interference with subsequent tests, since, as we know, resources often change the state of the machine, or which causes excessive slowness (eg: spawning new vm's for each test) since that would be too slow. It is highly likely that we'll want to use the txtar format, similarly to how we did with TestAstFunc2. Alternate proposals for the structure of the test are welcome if there is a better approach available. For example we want to test that a user resource with particular params produces a desired result on a machine. Or that a certain combination of params causes an error at resource Validation, or that a
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to purpleidea/mgmt, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of purpleidea/mgmt acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 7.4% were successfully merged into the primary branch.
purpleidea/mgmt has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 46.2 places purpleidea/mgmt in the Solid tier.
The external pull request merge rate is 7.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, purpleidea/mgmt currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for purpleidea/mgmt are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.