chrisryugj/kordoc - Open Source PR Review Scorecard

모두 파싱해버리겠다 — HWP·HWPX·PDF·Office 문서를 Markdown으로. 양식 자동 채우기와 신구대조를 갖춘 CLI·MCP 서버 | Convert Korean documents (HWP, HWPX, PDF, Office) to Markdown — CLI and MCP server with form filling and diff

C-Rank Grade: B (Solid) - 43/100

External PR Merge Rate: 70%

Response Time: 10d

First Timer Success: 60%

Frequently Asked Questions

Is chrisryugj/kordoc welcoming to first-time open-source contributors?

chrisryugj/kordoc has a recorded first-timer success rate of 60.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in chrisryugj/kordoc respond to incoming external pull requests in approximately 247.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 43.3 C-Rank™ score (B Tier) represent?

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 43.3 places chrisryugj/kordoc in the B tier.

What is the external contributor pull request merge rate for chrisryugj/kordoc?

The external contributor pull request merge rate for chrisryugj/kordoc is 69.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in chrisryugj/kordoc?

chrisryugj/kordoc does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

chrisryugj
chrisryugj/kordocBSolid1.7k
GitHub
Back to Explorer
chrisryugj

chrisryugj/kordoc

1,733
BSolid(43/100)TypeScript

모두 파싱해버리겠다 — HWP·HWPX·PDF·Office 문서를 Markdown으로. 양식 자동 채우기와 신구대조를 갖춘 CLI·MCP 서버 | Convert Korean documents (HWP, HWPX, PDF, Office) to Markdown — CLI and MCP server with form filling and diff

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active TypeScript repository in chrisryugj/kordoc with ongoing community development and issue triage.

Top PR Submission Do's

  • Ensure code complies with TypeScript style conventions
  • Keep PRs scoped and well-documented

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without context
  • Do not break existing automated test suites
Response Velocity
10 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
69.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
60.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
69.7%
Merge Gauge
60.0%
1st-Timer
Community Vibe46/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for chrisryugj/kordoc
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/chrisryugj/kordoc)](https://getmerged.abhishekco.de/chrisryugj/kordoc?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for chrisryugj/kordoc.

View all good first issues directly on GitHub

Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for chrisryugj/kordoc

When evaluating whether to contribute to chrisryugj/kordoc, 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 chrisryugj/kordoc acknowledge new external contributions in approximately 10 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to chrisryugj/kordoc

01

Is chrisryugj/kordoc welcoming to first-time open-source contributors?

chrisryugj/kordoc has a recorded first-timer success rate of 60.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~10 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 43.3 C-Rank™ score represent?

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 43.3 places chrisryugj/kordoc in the Solid tier.

04

What is the external contributor pull request merge rate for chrisryugj/kordoc?

The external pull request merge rate is 69.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in chrisryugj/kordoc?

chrisryugj/kordoc does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for chrisryugj/kordoc 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.