An open-source framework for detecting, redacting, masking, and anonymizing sensitive data (PII) across text, images, and structured data. Supports NLP, pattern matching, and customizable pipelines.
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 51%
Response Time: 2d
First Timer Success: 58%
data-privacy-stack/presidio has a recorded first-timer success rate of 58.1%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in data-privacy-stack/presidio respond to incoming external pull requests in approximately 39.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 55.0 places data-privacy-stack/presidio in the B tier.
The external contributor pull request merge rate for data-privacy-stack/presidio is 51.2%, based on public PR activity from non-core contributors.
data-privacy-stack/presidio currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (70% critical review signals). Ensure PRs strictly follow guidelines before requesting review in data-privacy-stack/presidio.
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/data-privacy-stack/presidio?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (64% approval). Large PRs (>500 lines) take ~187 hours (23% approval). Keep your diff compact for rapid review.
Two related behaviors observed on presidio-analyzer 2.2.364 (ghcr.io/data-privacy-stack/presidio-analyzer:2.2.364, default configuration, language en). Unsupported entity silently ignored POST /analyze {"text":"codice fiscale RSSMRA85M01H501Q, IBAN IT60X0542811101000000123456","language":"en","entities":["IT_FISCAL_CODE","IBAN_CODE"]} -> 200, [{"entity_type":"IBAN_CODE", ...}] IT_FISCAL_CODE is not in the response and nothing signals that it could not be served. Compare: {"text":"...","language":"en","entities":["IT_FISCAL_CODE"]} -> 500, {"error":"No matching recognizers were found to serve the request."} So the caller gets an error only when the unsupported entity is the sole one requested. In a gateway or DLP integration this is a footgun: an operator adds IT_FISCAL_CODE to the block list, the service keeps answering 200, and fiscal codes flow through unscanned. I measured exactly this on two LLM gateways that embed Presidio (LiteLLM and GoModel): 11 out of 11 positions leaked
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 data-privacy-stack/presidio, 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 data-privacy-stack/presidio acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 51.2% were successfully merged into the primary branch.
data-privacy-stack/presidio has a recorded first-timer success rate of 58.1%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 55.0 places data-privacy-stack/presidio in the Solid tier.
The external pull request merge rate is 51.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, data-privacy-stack/presidio currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for data-privacy-stack/presidio 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.