ESLint plugin about ECMAScript syntactic features.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 100%
Response Time: 3h
First Timer Success: 100%
eslint-community/eslint-plugin-es-x 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.
Maintainers in eslint-community/eslint-plugin-es-x respond to incoming external pull requests in approximately 3.4 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 59.5 places eslint-community/eslint-plugin-es-x in the A tier.
The external contributor pull request merge rate for eslint-community/eslint-plugin-es-x is 100.0%, based on public PR activity from non-core contributors.
eslint-community/eslint-plugin-es-x currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
ESLint plugin about ECMAScript syntactic features.
Collaborative maintainer environment in eslint-community/eslint-plugin-es-x. Reviews community pull requests with focus on project quality.
Discussions in eslint-community/eslint-plugin-es-x 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/eslint-community/eslint-plugin-es-x?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~16 hours (45% approval). Keep your diff compact for rapid review.
(While I chip away at migrating to TypeScript #327, I learned that) the eslint-internal plugin in this repository is vendored copy of eslint-plugin-mysticatea with flat config support added. Comments here eslint-community/eslint-plugin-mysticatea#183 seem to indicate that plugin could be deprecated. I would like to do the following: We can replace all the rules in rules/: my-block-scoped-var -> var is banned by no-var. Otherwise, it's collectively handled by block-scoped-var, no-undef, no-redeclare, no-shadow, etc. other ESLint built-in rules. my-no-instanceof-array -> unicorn/no-instanceof-builtins my-no-instanceof-wrapper -> unicorn/no-instanceof-builtins my-no-literal-call -> will be caught by TypeScript my-no-this-in-static -> no-restricted-syntax with the following options: { "no-restricted-syntax": ["error", { "selector": "MethodDefinition[static=true] ThisExpression", "message": "Unexpected 'this' in static method." }, { "selector": "MethodDefinition[static=
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 eslint-community/eslint-plugin-es-x, 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 eslint-community/eslint-plugin-es-x acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
eslint-community/eslint-plugin-es-x 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.
The initial maintainer response time averages ~3 hours. 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 59.5 places eslint-community/eslint-plugin-es-x in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eslint-community/eslint-plugin-es-x currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for eslint-community/eslint-plugin-es-x 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.