One database for user-user (follows), user-item (likes), and item-item (related items) interactions — precomputed at write time, served as simple lookups
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 83%
Response Time: 13h
First Timer Success: 100%
kakao/actionbase 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 kakao/actionbase respond to incoming external pull requests in approximately 12.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 65.5 places kakao/actionbase in the A tier.
The external contributor pull request merge rate for kakao/actionbase is 83.3%, based on public PR activity from non-core contributors.
kakao/actionbase does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in kakao/actionbase. Ensure PR scope matches issue requirements closely before requesting review.
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/kakao/actionbase?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (96% approval). Large PRs (>500 lines) take ~61 hours (38% approval). Keep your diff compact for rapid review.
Background The CLI was originally written in Kotlin, then converted to Go for easier distribution. We used AI for the conversion. It works, but honestly, we are not confident in Go—we do not know if the code is idiomatic or follows best practices. We need help from Go developers. If you see something wrong or weird, please tell us. The `internal/util` package has only one test file (`truncate_test.go`), which was also written by AI. Tasks Each item can be submitted as a separate PR. `util/filters.go` (12 LOC, Easy) `util/formatter.go` (~50 LOC, Easy) `util/strings.go` (~30 LOC, Easy) `util/arguments.go` (110 LOC, Medium) `util/table_printer.go` (~80 LOC, Medium) How to Contribute Comment below to claim an item Branch: `test/cli-util-` PR title: `test(cli): add tests for util/` One file per PR Run `cd cli && make test` Done When Test file at `cli/internal/util/_test.go` Public functions covered Tests pass Notes Code improvements are welcome—open a separate issue or includ
Background XXHash32Wrapper class lacks direct unit tests. While it is used in other tests (EdgeIndexMapperTest, EdgeStateMapperTest, V2MultiEdgeBulkLoadTest), there are no dedicated tests that verify its core functionality. Task Add unit tests for XXHash32Wrapper class. File path: core/src/main/kotlin/com/kakao/actionbase/core/codec/XXHash32Wrapper.kt (35 LOC) Test targets: hash(bytes, offset, length) - Hash byte array with offset and length stringHash(string) - Hash string value insertTsHash / deleteTsHash - Verify constant hash values create(seed) - Factory method with custom seed Done When Test file created at core/src/test/kotlin/com/kakao/actionbase/core/codec/XXHash32WrapperTest.kt All public methods are covered with tests. Tests pass with ./gradlew :core:test. Notes Suggested test cases: hash() returns consistent value for same input hash() returns different values for different inputs stringHash() returns consistent value for same string insertTsHash and deleteTsHash ar
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 kakao/actionbase, 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 kakao/actionbase acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
kakao/actionbase 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 ~12 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 65.5 places kakao/actionbase in the Welcoming tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kakao/actionbase does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for kakao/actionbase 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.