kristoff-it/superhtml - Open Source PR Review Scorecard

HTML Validator, Formatter, LSP, and Templating Language Library

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

External PR Merge Rate: 71%

Response Time: 18d

First Timer Success: 100%

Frequently Asked Questions

Is kristoff-it/superhtml welcoming to first-time open-source contributors?

kristoff-it/superhtml has a recorded first-timer success rate of 100.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 kristoff-it/superhtml respond to incoming external pull requests in approximately 435.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 43.5 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.5 places kristoff-it/superhtml in the B tier.

What is the external contributor pull request merge rate for kristoff-it/superhtml?

The external contributor pull request merge rate for kristoff-it/superhtml is 71.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in kristoff-it/superhtml?

kristoff-it/superhtml currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

kristoff-it
kristoff-it/superhtmlBSolid1.4k
GitHub
Back to Explorer
kristoff-it

kristoff-it/superhtml

1,362
BSolid(43/100)Zig

HTML Validator, Formatter, LSP, and Templating Language Library

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 Zig repository in kristoff-it/superhtml with ongoing community development and issue triage.

Top PR Submission Do's

  • Ensure code complies with Zig 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
18 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
71.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
71.4%
Merge Gauge
100.0%
1st-Timer
Community Vibe59/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

SuperHTML Version 0.6.2 Steps to Reproduce and Observed Behavior <link rel="apple-touch-startup-image" href="..." > is unrecognized and show error (while apple-touch-icon does not) Apple specific attributes are described here Expected Output according to the HTML spec Apple specific attributes should not throw errors

📅 Opened May 6, 2026💬 1 comment
Quality: 40/100Contribute
Looking for more Zig beginner tasks?Explore Zig 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 kristoff-it/superhtml

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

Frequently Asked Questions - Contributing to kristoff-it/superhtml

01

Is kristoff-it/superhtml welcoming to first-time open-source contributors?

kristoff-it/superhtml has a recorded first-timer success rate of 100.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 ~18 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 43.5 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.5 places kristoff-it/superhtml in the Solid tier.

04

What is the external contributor pull request merge rate for kristoff-it/superhtml?

The external pull request merge rate is 71.4%. 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 kristoff-it/superhtml?

Yes, kristoff-it/superhtml currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for kristoff-it/superhtml 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.