A minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 23%
Response Time: -
First Timer Success: 57%
PrivateBin/PrivateBin has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PrivateBin/PrivateBin respond to incoming external pull requests in approximately 0.0 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 58.1 places PrivateBin/PrivateBin in the A tier.
The external contributor pull request merge rate for PrivateBin/PrivateBin is 23.4%, based on public PR activity from non-core contributors.
PrivateBin/PrivateBin currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in PrivateBin/PrivateBin.
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/PrivateBin/PrivateBin?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (29% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Currently, this project does not support RTL bidirectional rendering, which limits its usability for RTL text. I believe we can generate a good-enough implementation for this feature using Codex. Would the project maintainers be open to accepting a Pull Request by Codex?
Due to the different lengths of words in different languages, the words do not fit in the input fields. The input fields need to be moved to the second line. That is, automatic scaling to the size of the window should be implemented.
The problem Server-side User Agents Crawler and Spider blocking to prevent leakage of shared documents/pastes The solution Suggest UA Block List in the webserver configuration in wiki at for an apache server configuration. Alternatives Additionally for the container images, the settings should go into either: nginx webserver configuration nginx unit configuration Additional context As suggested by @elrido in #1759 (comment)
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 PrivateBin/PrivateBin, 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 PrivateBin/PrivateBin acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 23.4% were successfully merged into the primary branch.
PrivateBin/PrivateBin has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 58.1 places PrivateBin/PrivateBin in the Welcoming tier.
The external pull request merge rate is 23.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PrivateBin/PrivateBin 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 PrivateBin/PrivateBin 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.