tirreno is an open-source framework for building sovereign security, compliance and fraud prevention applications. Detect account takeovers, cyberfraud and business logic abuse inside your product.
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: -
tirrenotechnologies/tirreno 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 tirrenotechnologies/tirreno 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 48.2 places tirrenotechnologies/tirreno in the B tier.
The external contributor pull request merge rate for tirrenotechnologies/tirreno is 100.0%, based on public PR activity from non-core contributors.
tirrenotechnologies/tirreno currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in tirrenotechnologies/tirreno welcoming community pull requests and bug fixes.
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/tirrenotechnologies/tirreno?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (45% approval). Keep your diff compact for rapid review.
A CSV export would be a useful enhancement — we want the full filtered result, not just the visible page. The Models/Grid/*/Query.php classes already build filtered, ordered SQL. Reuse them with the limit lifted and stream the result. Use fputcsv() PHP built-in function to produce CSV lines. UI: export button sits to the right of the table title, next to the refresh button. Disabled while an export is running so users can't fire off several by accident. What's needed: new route per grid, or one /csv_export taking the same filter params the grid uses; reuse assertCanView(): export must not become an RBAC bypass, and must stay scoped to the current API key; stream rows, don't buffer: the existing execQuery() returns a full array, which will OOM on large exports. Use a cursor or keyset pagination and flush as you go; server-side lock: one export in flight per operator, with a timeout so a stuck job doesn't block them permanently. The disabled button is UX only — the endpoint can stil
F3 Dictionary is already there app/Dictionary/en/, and DictManager builds paths from LOCALES + LANGUAGE. Both are hardcoded in index.php, so today the only way to change language is editing source. What's needed: language column on dshb_operators; migration in app/Updates/; set default language for operator guest as en. set language in selector in Settings, right after Time zone; set language in selector in Sign UP, right after Time zone; check ui/js/ for hardcoded strings; Goal: adding a language means adding app/Dictionary// and nothing else. Missing keys fall back to english.
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 tirrenotechnologies/tirreno, 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 tirrenotechnologies/tirreno acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
tirrenotechnologies/tirreno 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 ~-. 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 48.2 places tirrenotechnologies/tirreno in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tirrenotechnologies/tirreno 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 tirrenotechnologies/tirreno 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.