vfarcic/dot-ai - Open Source PR Review Scorecard

Intelligent dual-mode agent for deploying applications to ANY Kubernetes cluster through dynamic discovery and plain English governance

C-Rank Grade: A (Welcoming) - 69/100

External PR Merge Rate: 90%

Response Time: 18h

First Timer Success: 67%

Frequently Asked Questions

Is vfarcic/dot-ai welcoming to first-time open-source contributors?

vfarcic/dot-ai has a recorded first-timer success rate of 66.7%. Repositories ranked A 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 vfarcic/dot-ai respond to incoming external pull requests in approximately 18.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 69.0 C-Rank™ score (A 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 69.0 places vfarcic/dot-ai in the A tier.

What is the external contributor pull request merge rate for vfarcic/dot-ai?

The external contributor pull request merge rate for vfarcic/dot-ai is 89.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in vfarcic/dot-ai?

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

vfarcic
vfarcic/dot-aiAWelcoming335
GitHub
Back to Explorer
vfarcic

vfarcic/dot-ai

335
AWelcoming(69/100)TypeScript

Intelligent dual-mode agent for deploying applications to ANY Kubernetes cluster through dynamic discovery and plain English governance

Compare
Jump to:
Response Velocity
18 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
89.8%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
66.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

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

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Problem Two related issues in the Copilot credential path. The first is a concrete test bug with a one-line fix; the second is a design question worth a deliberate decision. 1. it.skipIf gates on token presence, so npm run test:unit fails for anyone with a classic PAT tests/unit/core/providers/vercel-provider.copilot.test.ts:136-143: // Live e2e — only runs when a real token is available it.skipIf(!process.env.GITHUB_COPILOT_TOKEN && !process.env.GH_TOKEN && !process.env.GITHUB_TOKEN)( 'e2e: resolver returns a usable token from env', () => { const resolver = makeCopilotCredentialResolver(); const token = resolver.resolve(); expect(token).toMatch(/^(gho_|ghu_)/); } ); The gate un-skips whenever any of those three variables is merely set, but the resolver only accepts gho_* / ghu_* and deliberately rejects ghp_* / github_pat_* (src/core/providers/copilot-token-exchanger.ts:55-61). So a developer with a classic PAT in GITHUB_TOKEN — very common, it's what gh auth lo

📅 Opened Aug 14, 2026💬 4 comments
Quality: 90/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 vfarcic/dot-ai

When evaluating whether to contribute to vfarcic/dot-ai, 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 vfarcic/dot-ai acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.8% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to vfarcic/dot-ai

01

Is vfarcic/dot-ai welcoming to first-time open-source contributors?

vfarcic/dot-ai has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming 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 ~18 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.0 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 69.0 places vfarcic/dot-ai in the Welcoming tier.

04

What is the external contributor pull request merge rate for vfarcic/dot-ai?

The external pull request merge rate is 89.8%. 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 vfarcic/dot-ai?

Yes, vfarcic/dot-ai 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 vfarcic/dot-ai 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.