A luxurious package manager for Lua
C-Rank Grade: S (Elite) - 79/100
External PR Merge Rate: 93%
Response Time: 4h
First Timer Success: 88%
lumen-oss/lux has a recorded first-timer success rate of 87.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lumen-oss/lux respond to incoming external pull requests in approximately 3.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 79.2 places lumen-oss/lux in the S tier.
The external contributor pull request merge rate for lumen-oss/lux is 92.9%, based on public PR activity from non-core contributors.
lumen-oss/lux currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in lumen-oss/lux. Prompt code reviews with positive guidance for new contributors.
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/lumen-oss/lux?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~17 hours (42% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
Encrypted notebook
A cross platform mDNS-Browser app written in Rust using tauri and leptos
Rust-powered Svelte ecosystem
Running tests with pandoc requires some boilerplate. We have a busted-nlua test backend for Neovim. Perhaps it's worth adding a busted-pandoc test backend, too.
lx upload generates a rockspec and uploads it. Perhaps we should add a --test-install flag to do a test install into a temp directory before uploading.
For use with nix, it would be useful to have a lx generate-lockfile command that generates a project lockfile from a rockspec or package on luarocks.org
lx run currently only runs packages installed to the project tree. It should also include test dependencies, such as luacov. Discussed in #1315 Originally posted by ALameLlama January 27, 2026 Hey, I'm a little confused. so I've been running lx test -- --coverage and that's been working great. I can see it generate the luacov.stats.out and then I can run luacov which then generates me the report. this is working because in my nix dev shell I've got (luajit.withPackages (ps: with ps; [ luacov ])) which installs it so it's accessible globally. but lux installs this into .lux already is there a way to run stuff out of these dirs? such as test_dependacies e.g if I also wanted to install something like https://github.com/daurnimator/luacov-reporter-lcov or https://github.com/spacewander/luacov-console as test deps, would I be able to run this via some lux command I just cant find?
lux-lib lacks some documentation. This issue is for tracking places where we should add some doc comments. Config ConfigBuilder Config
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 lumen-oss/lux, 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 lumen-oss/lux acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.9% were successfully merged into the primary branch.
lumen-oss/lux has a recorded first-timer success rate of 87.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 79.2 places lumen-oss/lux in the Elite tier.
The external pull request merge rate is 92.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lumen-oss/lux currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lumen-oss/lux 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.