jank is the native Clojure dialect with seamless C++ interop.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 87%
Response Time: -
First Timer Success: 100%
jank-lang/jank has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jank-lang/jank 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 66.3 places jank-lang/jank in the A tier.
The external contributor pull request merge rate for jank-lang/jank is 86.6%, based on public PR activity from non-core contributors.
jank-lang/jank currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in jank-lang/jank. Prompt code reviews with positive guidance for new contributors.
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/jank-lang/jank?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 17:00 to 21:00 UTC (17:00 - 21: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 (39% approval). Keep your diff compact for rapid review.
Clojure doesn't allow either of these: ❯ clj Clojure 1.12.4 user=> (let [.-foo 3] (println .-foo)) Syntax error (ClassFormatError) compiling fn* at (REPL:1:1). Illegal field name "._foo" in class user$eval134 user=> (let [.foo 3] (println .foo)) Syntax error (ClassFormatError) compiling fn* at (REPL:1:1). Illegal field name ".foo" in class user$eval136 We should do the same. Right now, we allow them during analysis and then fail during codegen, since we're not expecting . in any symbols and we don't munge that character. We shouldn't need to fix the munging if we prevent this during analysis anyway. These member symbols can only be used in call position. Looks like we do this in some cases, but not others. user=> (println .-foo) ─ analyze/invalid-cpp-position ───────────────────────────────────────────────────────────────────── error: Unable to
jank health check ─ system ─────────────────────────────────────────────────────────────────────────────────────────── ─ ✅ operating system: macos ─ ✅ default triple: arm64-apple-darwin24.6.0 ─ jank install ───────────────────────────────────────────────────────────────────────────────────── ─ ✅ jank version: jank-0.1-alpha ─ ⚠️ jank assertions are enabled; performance will be impacted ─ ✅ jank resource dir: ../lib/jank/0.1 ─ ✅ jank resolved resource dir: /Users/emma/programming/jank/compiler+runtime/build/../lib/jank/0.1 (ignored for dev build) ─ ✅ jank user cache dir: /Users/emma/.cache/jank/arm64-apple-d
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 jank-lang/jank, 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 jank-lang/jank acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.6% were successfully merged into the primary branch.
jank-lang/jank has a recorded first-timer success rate of 100.0%. 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 66.3 places jank-lang/jank in the Welcoming tier.
The external pull request merge rate is 86.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jank-lang/jank 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 jank-lang/jank 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.