njelich/LinkOff - Open Source PR Review Scorecard

Cleans the LinkedIn feed based on keywords and filters.

C-Rank Grade: D (Risky) - 23/100

External PR Merge Rate: -

Response Time: 2d

First Timer Success: -

Frequently Asked Questions

Is njelich/LinkOff welcoming to first-time open-source contributors?

njelich/LinkOff 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.

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

Maintainers in njelich/LinkOff respond to incoming external pull requests in approximately 39.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 23.1 C-Rank™ score (D 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 23.1 places njelich/LinkOff in the D tier.

What is the external contributor pull request merge rate for njelich/LinkOff?

The external contributor pull request merge rate for njelich/LinkOff is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in njelich/LinkOff?

njelich/LinkOff currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

njelich
njelich/LinkOffD•Risky227
GitHub
Back to Explorer
njelich

njelich/LinkOff

227
InactiveD•Risky(23/100)Low Sample (<20 PRs)CSS

Cleans the LinkedIn feed based on keywords and filters.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in njelich/LinkOff. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in njelich/LinkOff focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Two problems: On the main LinkedIn feed, "Commented On" posts are not being filtered out, despite having set the "Hide commented on by connections" flag in LinkOff. All other filters appear to be working fine. Despite setting the "Hide promoted" in the jobs section in LinkOff, promoted jobs are not getting filtered. 2.a. They are not filtered from the first jobs related screen in LinkedIn where it offers suggestions and other junk. 2.b. They are also not filtered out of the list of jobs returned if I do a search. I found one workaround for removing them from the list of jobs returned for a search by 1) running the search; 2) go to LinkOff and turn off the Hide Promoted flag 3) refresh the browser window 4) turn the Hide Promoted flag back on in LinkOff 5) refresh the browser again. This workaround does not persist though, you would need to re-do it every time you did a job search, so it is not a long term fix. Environment (please complete the following information): Linux Mint Br

📅 Opened Jul 30, 2026💬 5 comments
Quality: 65/100Contribute
Looking for more CSS beginner tasks?Explore CSS 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 njelich/LinkOff

When evaluating whether to contribute to njelich/LinkOff, 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 njelich/LinkOff acknowledge new external contributions in approximately 1 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.

Frequently Asked Questions - Contributing to njelich/LinkOff

01

Is njelich/LinkOff welcoming to first-time open-source contributors?

njelich/LinkOff 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.

02

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

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

03

What does the 23.1 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 23.1 places njelich/LinkOff in the Risky tier.

04

What is the external contributor pull request merge rate for njelich/LinkOff?

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.

05

Are there beginner Good First Issues open in njelich/LinkOff?

Yes, njelich/LinkOff currently has 1 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 njelich/LinkOff 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.