Lightweight multi-format artifact registry. 15 formats: Docker, Maven, npm, PyPI, Cargo, Go, Raw, RubyGems, Terraform, Ansible Galaxy, NuGet, Pub, Conan, RPM, and Debian/APT. Single binary, zero dependencies, < 50 MB RAM idle.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 57%
Response Time: 3d
First Timer Success: 67%
getnora-io/nora has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in getnora-io/nora respond to incoming external pull requests in approximately 82.2 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 57.6 places getnora-io/nora in the A tier.
The external contributor pull request merge rate for getnora-io/nora is 57.4%, based on public PR activity from non-core contributors.
getnora-io/nora does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in getnora-io/nora. Prompt code reviews with positive guidance for new contributors.
Discussions in getnora-io/nora focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/getnora-io/nora?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 05:00 UTC (05: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 ~53 hours (72% approval). Large PRs (>500 lines) take ~395 hours (26% approval). Keep your diff compact for rapid review.
What's missing release.yml builds the .deb and .rpm with nfpm 2.46.3 at tag time and uploads them. Nothing ever installs one. No job unpacks a package, puts it on a clean system, starts the service, or runs lintian. A change under dist/ therefore passes every check we have and is only validated when a user installs the release. That is not hypothetical: #1022 found four aliased-location lintian errors in the shipped .deb — the unit file installed to /lib/systemd/system, which Debian policy has forbidden since the /usr merge. It shipped in every release until #1023. The first revision of #1023 also moved the state directories to /usr/var/lib/nora and /usr/var/log/nora. That package installs cleanly and puts runtime state in a path nothing else uses. It would have gone green. What I ran by hand while reviewing #1023 Privileged debian:trixie container with systemd as PID 1 (systemd 257, dpkg 1.22.22), both packages built with the pinned nfpm from the respective trees, the same binary
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 getnora-io/nora, 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 getnora-io/nora acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.4% were successfully merged into the primary branch.
getnora-io/nora has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 57.6 places getnora-io/nora in the Welcoming tier.
The external pull request merge rate is 57.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
getnora-io/nora does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for getnora-io/nora 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.