desktop app to browse and analyze your Claude Code conversation history
C-Rank Grade: S (Elite) - 69/100
External PR Merge Rate: 76%
Response Time: -
First Timer Success: 71%
jhlee0409/claude-code-history-viewer has a recorded first-timer success rate of 71.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jhlee0409/claude-code-history-viewer 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 69.4 places jhlee0409/claude-code-history-viewer in the S tier.
The external contributor pull request merge rate for jhlee0409/claude-code-history-viewer is 76.2%, based on public PR activity from non-core contributors.
jhlee0409/claude-code-history-viewer currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
desktop app to browse and analyze your Claude Code conversation history
Strict review standards in jhlee0409/claude-code-history-viewer. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in jhlee0409/claude-code-history-viewer focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/jhlee0409/claude-code-history-viewer?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (95% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
Feature request: option to expand long messages by default Problem When an assistant (or user) message is longer than 3 lines, it is collapsed by default and only the first 3 lines are shown, with a "Show more..." button to expand. For messages that are mostly prose, having to click "Show more..." every time makes long replies tedious to read. Where the behavior lives This is currently hardcoded in src/components/messageRenderer/MessageContentDisplay.tsx: LINE_LIMIT = 3 — any text with more than 3 lines gets a collapsed preview. useCaptureExpandState("content", false) — the initial expand state is false (collapsed). There is no user-facing setting to change either the threshold or the default state. Expand state is stored in-memory only (src/store/expandRegistryStore.ts), so it resets on every session open. Proposed solution Add a settings option such as "Expand long messages by default" (or a configurable line limit). When enabled: Long messages render fully expanded by default
Right now the way this is packaged/distributed on Linux is as an appimage, but appimages have a lot of problems, including: No package manager/centralized update mechanism, Huge size because of bundled dependencies, Lack of security/sandboxing. Could we get a Flatpak (or maybe a .deb) as well/instead?
日常开发主要用的claude code和Hermes，希望可以支持Hermes agent
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 jhlee0409/claude-code-history-viewer, 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 jhlee0409/claude-code-history-viewer acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.2% were successfully merged into the primary branch.
jhlee0409/claude-code-history-viewer has a recorded first-timer success rate of 71.4%. Repositories ranked Elite 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 69.4 places jhlee0409/claude-code-history-viewer in the Elite tier.
The external pull request merge rate is 76.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jhlee0409/claude-code-history-viewer currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jhlee0409/claude-code-history-viewer 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.