ESLint plugin with rules that help validate proper imports.
C-Rank Grade: C (Moderate) - 26/100
External PR Merge Rate: 88%
Response Time: 18h
First Timer Success: 100%
import-js/eslint-plugin-import has a recorded first-timer success rate of 100.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in import-js/eslint-plugin-import respond to incoming external pull requests in approximately 18.2 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 26.5 places import-js/eslint-plugin-import in the C tier.
The external contributor pull request merge rate for import-js/eslint-plugin-import is 87.5%, based on public PR activity from non-core contributors.
import-js/eslint-plugin-import currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
ESLint plugin with rules that help validate proper imports.
Collaborative maintainer environment in import-js/eslint-plugin-import. Reviews community pull requests with focus on project quality.
Discussions in import-js/eslint-plugin-import 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/import-js/eslint-plugin-import?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (96% approval). Large PRs (>500 lines) take ~87 hours (39% approval). Keep your diff compact for rapid review.
Inside some of my unit tests I have import code (using Bun macro import annotation) like: import { compile } from "../src/macro.ts" with { type: "macro" }; import { compile as compileNoMacro } from "../src/macro.ts"; This currently reports an error, even though the import attributes are different. It shouldn't be restricted to just the "type" attribute key, any differing import attributes should be treated as a unique import even with the same import path. I'd like to see a new option added to import/no-duplicates (and enabled by default) to differentiate import by their import attributes.
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 import-js/eslint-plugin-import, 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 import-js/eslint-plugin-import acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.5% were successfully merged into the primary branch.
import-js/eslint-plugin-import has a recorded first-timer success rate of 100.0%. Repositories ranked Moderate typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 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 26.5 places import-js/eslint-plugin-import in the Moderate tier.
The external pull request merge rate is 87.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, import-js/eslint-plugin-import 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 import-js/eslint-plugin-import 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.