AprilSylph/XKit-Rewritten - Open Source PR Review Scorecard

🧰 The enhancement suite for Tumblr's new web interface

C-Rank Grade: A (Welcoming) - 55/100

External PR Merge Rate: 68%

Response Time: 7d

First Timer Success: 100%

Frequently Asked Questions

Is AprilSylph/XKit-Rewritten welcoming to first-time open-source contributors?

AprilSylph/XKit-Rewritten 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.

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

Maintainers in AprilSylph/XKit-Rewritten respond to incoming external pull requests in approximately 178.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 55.4 C-Rank™ score (A 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 55.4 places AprilSylph/XKit-Rewritten in the A tier.

What is the external contributor pull request merge rate for AprilSylph/XKit-Rewritten?

The external contributor pull request merge rate for AprilSylph/XKit-Rewritten is 68.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in AprilSylph/XKit-Rewritten?

AprilSylph/XKit-Rewritten currently has 25 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

AprilSylph
AprilSylph/XKit-RewrittenA•Welcoming376
GitHub
Back to Explorer
AprilSylph

AprilSylph/XKit-Rewritten

376
InactiveA•Welcoming(55/100)JavaScript

🧰 The enhancement suite for Tumblr's new web interface

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in AprilSylph/XKit-Rewritten.

Top PR Submission Do's

  • •Verify all existing package test suites run cleanly
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
7 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
68.0%
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
68.0%
Merge Gauge
100.0%
1st-Timer
Community Vibe57/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Platform n/a Browser n/a Addon version n/a Details I haven't managed to reproduce this in a supported browser, but it occurred while doing some off-label testing and I do think logically it should be possible to occur in any browser. Classic Footer can create duplicate post counts and reblog buttons the first time it is enabled in an installation. This is because its processPosts function doesn't have robust deduplication (it does not use filterPostElements with an excludeClass argument, and its removal code is separated from its addition code by two awaits, which means a possible race condition), and because it triggers this function in onStorageChanged. onStorageChanged will be called when its preferences are updated, which occurs the first time it is enabled in an installation, because we populate default preferences at that point.

📅 Opened Oct 10, 2026💬 0 comments
Quality: 90/100Contribute

Platform macOS 14.8.8 arm64 Browser Firefox 155.0.1 Addon version master (v1.3.7) Details If Classic Search is enabled and then disabled without ever seeing a search element, such as on a narrow viewport, searchInputParent is never defined as anything and this will throw: XKit-Rewritten/src/features/classic_search/index.js Lines 42 to 48 in a12e16e export const clean = async function () { pageModifications.unregister(replaceSearchForm); searchInputParent.appendChild(searchInputElement); removeElementsByClassName('classic-search'); $('.xkit-classic-search-done').removeClass('xkit-classic-search-done'); };

📅 Opened Sep 29, 2026💬 0 comments
Quality: 90/100Contribute

Platform MacOS Browser Firefox 155.0.1 Addon version master branch Details Typing something into the search box with Classic Search enabled and pressing enter navigates to a broken page.

📅 Opened Sep 9, 2026💬 0 comments
Quality: 75/100Contribute

Description Animated avatars, at time of writing, don't exist, but they narrowly won a recent poll on the tumblr engineering blog, so we could attempt to ship support in advance in case they do get implemented. Technically, the only code that actually has to be changed is this line, which per #1746 (and #1804) was in order to not put gif labels on non-animated gif avatars. (We do have the ability to check if gifs are animated, now, if we really want to be correct about this edge case.) XKit-Rewritten/src/features/accesskit/disable_gifs.js Line 192 in 2d561ce if (gifElement.closest(`${keyToCss('avatarImage', 'subAvatarImage')}, .block-editor-writing-flow`)) return; But this doesn't actually look great, imo; we probably want to make a UI that's better-looking than this: (I wouldn't mind so much if the only way to get an animated avatar was via workarounds, like it was that o

📅 Opened Aug 31, 2026💬 1 comment
Quality: 100/100Contribute

Description https://www.tumblr.com/engineering/825845466763837440/now-in-labs-full-screen-messaging-on-web Full-screen messaging: it's great; I probably would want to use it, at minimum, the vast majority of the time. Completely replacing current messaging with it would probably be a bit of a niche toggle for Tumblr to add (though I did comment suggesting this); I can't deny that there's legitimate utility in being able to use the traditional bubble system sometimes, so making the messaging sidebar item go straight to /messages is kind of a power user thing. That's what XKit tweaks are for, though, right? Note that full screen messages is a labs feature, but that I can tell, the labs toggle just adds the button to actually go to /messages; the route works fine either way. So if this were a tweak, it wouldn't actually have to check if the labs feature is enabled. (If the feature were removed from the site, it would be bad, though, and being a labs feature is presumably intended as a sig

📅 Opened Aug 24, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript 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 AprilSylph/XKit-Rewritten

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

Frequently Asked Questions - Contributing to AprilSylph/XKit-Rewritten

01

Is AprilSylph/XKit-Rewritten welcoming to first-time open-source contributors?

AprilSylph/XKit-Rewritten 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.

02

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

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

03

What does the 55.4 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 55.4 places AprilSylph/XKit-Rewritten in the Welcoming tier.

04

What is the external contributor pull request merge rate for AprilSylph/XKit-Rewritten?

The external pull request merge rate is 68.0%. 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 AprilSylph/XKit-Rewritten?

Yes, AprilSylph/XKit-Rewritten currently has 25 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 AprilSylph/XKit-Rewritten 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.