🐢 Open-Source Evaluation & Testing library for LLM Agents
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 61%
Response Time: 1d
First Timer Success: 40%
Giskard-AI/giskard-oss has a recorded first-timer success rate of 40.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Giskard-AI/giskard-oss respond to incoming external pull requests in approximately 28.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 57.3 places Giskard-AI/giskard-oss in the A tier.
The external contributor pull request merge rate for Giskard-AI/giskard-oss is 60.7%, based on public PR activity from non-core contributors.
Giskard-AI/giskard-oss currently has 1 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 Giskard-AI/giskard-oss.
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/Giskard-AI/giskard-oss?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~19 hours (76% approval). Large PRs (>500 lines) take ~137 hours (27% approval). Keep your diff compact for rapid review.
Problem The public checks API is async-only. In a normal Python script, users must write asyncio.run(scenario.run()) (and the same applies to Suite and TestCase). This is boilerplate for a common synchronous entry point. Proposed change Add run_sync(...) to the public, user-facing runnable types in giskard-checks: Scenario Suite TestCase Keep the existing async run(...) API unchanged. Use one shared internal helper or mixin so the loop-detection behavior and error message stay consistent. Example: result = scenario.run_sync() results = suite.run_sync(parallel=True, verbose=False) Required behavior In a plain synchronous script or synchronous test, run_sync(*args, **kwargs) returns the same result as asyncio.run(self.run(*args, **kwargs)). It forwards all positional and keyword arguments exactly to run. It must work from a non-main thread that has no running event loop. If called while an asyncio event loop is already running (Jupyter/IPython notebooks, async pytest tests, async web
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 Giskard-AI/giskard-oss, 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 Giskard-AI/giskard-oss acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.7% were successfully merged into the primary branch.
Giskard-AI/giskard-oss has a recorded first-timer success rate of 40.0%. Repositories ranked Welcoming 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 57.3 places Giskard-AI/giskard-oss in the Welcoming tier.
The external pull request merge rate is 60.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Giskard-AI/giskard-oss 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 Giskard-AI/giskard-oss 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.