ESLint/Oxlint plugin to help you write better tailwindcss by improving readability with formatting rules and enforcing best practices with linting rules.
C-Rank Grade: D (Risky) - 21/100
External PR Merge Rate: -
Response Time: 3d
First Timer Success: -
schoero/eslint-plugin-better-tailwindcss has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in schoero/eslint-plugin-better-tailwindcss respond to incoming external pull requests in approximately 65.8 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 21.4 places schoero/eslint-plugin-better-tailwindcss in the D tier.
The external contributor pull request merge rate for schoero/eslint-plugin-better-tailwindcss is 0.0%, based on public PR activity from non-core contributors.
schoero/eslint-plugin-better-tailwindcss currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
ESLint/Oxlint plugin to help you write better tailwindcss by improving readability with formatting rules and enforcing best practices with linting rules.
Collaborative maintainer environment in schoero/eslint-plugin-better-tailwindcss. Reviews community pull requests with focus on project quality.
Discussions in schoero/eslint-plugin-better-tailwindcss 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/schoero/eslint-plugin-better-tailwindcss?utm_source=github&utm_medium=badge)
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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~43 hours (81% approval). Large PRs (>500 lines) take ~316 hours (29% approval). Keep your diff compact for rapid review.
Description Hi! I found this and some other issues, where we have this problem . lint:code: @sabdx/storybook:lint:code: Error: Internal error: Atomics.wait() failed: timed-out . lint:code: @sabdx/storybook:lint:code: Occurred while linting /builds/sab/sabdx/components/sabdx-ui/sabdx-ui-bibliotheken/apps/storybook/src/components/story-header.tsx:22 . lint:code: @sabdx/storybook:lint:code: Rule: "better-tailwindcss/enforce-canonical-classes" . lint:code: @sabdx/storybook:lint:code: at receiveMessageWithId (file:///builds/sab/sabdx/components/sabdx-ui/sabdx-ui-bibliotheken/node_modules/.pnpm/[email protected]/node_modules/synckit/lib/helpers.js:367:19) . lint:code: @sabdx/storybook:lint:code: at syncFn (file:///builds/sab/sabdx/components/sabdx-ui/sabdx-ui-bibliotheken/node_modules/.pnpm/[email protected]/node_modules/synckit/lib/helpers.js:385:54) . lint:code: @sabdx/storybook:lint:code: at getCanonicalClasses (file:///builds/sab/sabdx/components/sabdx-ui/sabdx-ui-bibliotheken/no
Description I'm encountering this issue where, when I run a lint check, sometimes it passes and sometimes it finds issues. I even wrote a script to run a bunch of lint checks over and over on the same code, and it really does seem to be nondeterministic. This is what Claude seems to think the root problem is: eslint-plugin-better-tailwindcss uses synckit worker threads to bridge Tailwind CSS's async API into synchronous ESLint rules. When ESLint processes many files, the worker encounters a race condition that causes it to silently fail. This failure corrupts the entire ESLint run — not just better-tailwindcss rules but ALL rules return 0 results. The behavior is non-deterministic: the same command run multiple times gives different results. The issue seems to be related to the number of files being checked. When I run it on fewer files, it catches the issues almost every time. For example, let's say I have 200 files to lint, if I lint them in batches of 10 files, it works (reports
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 schoero/eslint-plugin-better-tailwindcss, 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 schoero/eslint-plugin-better-tailwindcss acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
schoero/eslint-plugin-better-tailwindcss has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 21.4 places schoero/eslint-plugin-better-tailwindcss in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, schoero/eslint-plugin-better-tailwindcss currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for schoero/eslint-plugin-better-tailwindcss 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.