C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 81%
Response Time: 11h
First Timer Success: 60%
plengauer/Thoth has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in plengauer/Thoth respond to incoming external pull requests in approximately 10.7 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 66.1 places plengauer/Thoth in the A tier.
The external contributor pull request merge rate for plengauer/Thoth is 80.9%, based on public PR activity from non-core contributors.
plengauer/Thoth currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in plengauer/Thoth. Reviews community pull requests with focus on project quality.
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/plengauer/Thoth?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 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~52 hours (36% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Shell.
Cross-vendor messaging for CLI AI coding agents — let Claude Code, Codex, Gemini & Copilot talk to each other in one team. Bash + SQLite, no daemon, no framework.
Debian based ArkOS
Opinionated Niri bootc image
Problem The first step of the generate job in .github/workflows/refresh_demos.yml picks which .deb to install: { if [ "$GITHUB_EVENT" = release ]; then cat "$GITHUB_EVENT_PATH"; else curl --header "Authorization: Bearer ${{ github.token }}" https://api.github.com/repos/"$GITHUB_REPOSITORY"/releases/latest; fi; } \ | jq -r '.assets[] | select(.name | endswith("_amd64.deb")) | .url' \ | xargs wget ... -O package.deb GITHUB_EVENT is not a GitHub Actions environment variable. The documented ones are GITHUB_EVENT_NAME (the event) and GITHUB_EVENT_PATH (the payload file). $GITHUB_EVENT expands to the empty string, [ "" = release ] is always false, and the else branch always wins. Consequence: the workflow never uses the assets of the release that triggered it. It always downloads /releases/latest. The then branch and $GITHUB_EVENT_PATH are dead code. Evidence Release v5.60.2 triggered run #87 at 2026-08-22 18:58Z. The README it generated in #4097 reports: "telemetry.sdk.version": "5.61.1
Context The macOS support work in #3174 (and the follow-up PRs #3942–#3951) makes INSTALL.sh and the GitHub Action installer (actions/instrument/shared/install.sh) try Homebrew first on Darwin, then fall back to a tarball install if brew isn't present or the tap install fails: brew tap plengauer/opentelemetry-shell https://github.com/plengauer/Thoth brew install opentelemetry-shell That tap — plengauer/homebrew-opentelemetry-shell — doesn't exist yet, so today this always falls through to the tarball path. That's fine functionally (the tarball path is the one actually exercised by CI's macos-latest smoke test), but Homebrew is the more idiomatic macOS install experience and is worth having as the primary path eventually. What's already in place meta/homebrew/opentelemetry-shell.rb — a working formula. build-brew (in build.yml) already fills in its __VERSION__/__SHA256__ placeholders on every build and uploads the result as a homebrew-formula.<ref> artifact — it's just not pu
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 plengauer/Thoth, 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 plengauer/Thoth acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.9% were successfully merged into the primary branch.
plengauer/Thoth has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 hours. 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 66.1 places plengauer/Thoth in the Welcoming tier.
The external pull request merge rate is 80.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, plengauer/Thoth currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for plengauer/Thoth 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.