[Experimental] A fast, friendly linter for JavaScript, TypeScript, and more. ❤️🔥
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 71%
Response Time: -
First Timer Success: 50%
flint-fyi/flint has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in flint-fyi/flint respond to incoming external pull requests in approximately 0.0 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 67.8 places flint-fyi/flint in the A tier.
The external contributor pull request merge rate for flint-fyi/flint is 71.3%, based on public PR activity from non-core contributors.
flint-fyi/flint currently has 16 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
[Experimental] A fast, friendly linter for JavaScript, TypeScript, and more. ❤️🔥
Highly welcoming maintainers in flint-fyi/flint. Prompt code reviews with positive guidance for new contributors.
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/flint-fyi/flint?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (89% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
Documentation Report Checklist I have checked the latest main branch of the repository. I have searched for related issues and found none that matched my issue. Overview Renovate PR #3602 updates a dependency whose deno-lint rules no longer match packages/rule-data/src/data.json. packages/rule-data/src/data.test.ts fails on that PR until the data is synced. Missing from data.json (15): fresh-handler-export fresh-server-event-handlers no-await-in-sync-fn no-class-assign no-dupe-else-if no-import-prefix no-invalid-triple-slash-reference no-octal no-this-alias no-top-level-await no-unversioned-import prefer-primordials react-no-danger react-no-danger-with-children react-rules-of-hooks In data.json but no longer provided by deno-lint (4): button-has-type no-await-in-sync-fun no-case-assign no-invalid-triple-slash-references Additional Info Filed by the Rule Data Renovate workflow. This issue is updated in place while Renovate PRs keep reporting deno-lint gaps, so
Feature Request Checklist I am using the latest published version of all Flint packages. I have searched for related issues and found none that matched my issue. Overview Have one consistent, explicit mental model when writing tests. Bad: { code: "incorect", fileName: "src/example.txt", files: { "cspell.json": '{"words":["incorect"]}' }, }, Ok: { files: { "cspell.json": '{"words":["incorect"]}' }, "src/example.txt": "incorect", }, }, Also ok: "incorect" To be honest, it does feel a bit verbose to have to nest it under the files key, but AFAICT it's not actually more verbose, it just feels so. And it's vastly easier to see what's going on, and doesn't prioritize one file over others (relevant for MFA). Additional Info #3530 (comment)
Documentation Report Checklist I have checked the latest main branch of the repository. I have searched for related issues and found none that matched my issue. Overview Renovate PR #3668 updates a dependency whose @typescript-eslint rules no longer match packages/rule-data/src/data.json. packages/rule-data/src/data.test.ts fails on that PR until the data is synced. Missing from data.json (1): @typescript-eslint/no-unsafe-enum-assignment Additional Info Filed by the Rule Data Renovate workflow. This issue is updated in place while Renovate PRs keep reporting @typescript-eslint gaps, so the lists above reflect the latest failing run. To resolve: Add each missing rule to packages/rule-data/src/data.json, and remove stale references. For rules that shouldn't be skipped, file a new rule issue to track the Flint equivalent. Run pnpm --filter=rule-data sort-data. Push to the Renovate branch, or open a PR that bumps the dependency and closes this issue.
Documentation Report Checklist I have checked the latest main branch of the repository. I have searched for related issues and found none that matched my issue. Overview Renovate PR #3421 updates a dependency whose vue rules no longer match packages/rule-data/src/data.json. packages/rule-data/src/data.test.ts fails on that PR until the data is synced. Missing from data.json (1): vue/no-shadow-native-events Additional Info Filed by the Rule Data Renovate workflow. This issue is updated in place while Renovate PRs keep reporting vue gaps, so the lists above reflect the latest failing run. To resolve: Add each missing rule to packages/rule-data/src/data.json, and remove stale references. For rules that shouldn't be skipped, file a new rule issue to track the Flint equivalent. Run pnpm --filter=rule-data sort-data. Push to the Renovate branch, or open a PR that bumps the dependency and closes this issue.
Documentation Report Checklist I have checked the latest main branch of the repository. I have searched for related issues and found none that matched my issue. Overview Renovate PR #3435 updates a dependency whose solid rules no longer match packages/rule-data/src/data.json. packages/rule-data/src/data.test.ts fails on that PR until the data is synced. Missing from data.json (15): solid/no-accessor-as-prop solid/no-boolean-enumerated-attribute solid/no-browser-globals-in-server-function solid/no-invalid-server-capture solid/no-module-scope-reactive-primitive solid/no-restated-default-options solid/no-single-arg-create-effect solid/no-store-mutation-outside-setter solid/no-unused-signal solid/no-write-in-pure-computation solid/prefer-onSettled-for-side-effects solid/prefer-structured-class solid/removed-api solid/require-async-server-function solid/valid-use-server Additional Info Filed by the Rule Data Renovate workflow. This issue is updated in place while Renova
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 flint-fyi/flint, 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 flint-fyi/flint acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.3% were successfully merged into the primary branch.
flint-fyi/flint has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.8 places flint-fyi/flint in the Welcoming tier.
The external pull request merge rate is 71.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, flint-fyi/flint currently has 16 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for flint-fyi/flint 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.