southleft/figma-console-mcp - Open Source PR Review Scorecard

Your design system as an API. Connect AI to Figma for extraction, creation, and debugging.

C-Rank Grade: C (Moderate) - 30/100

External PR Merge Rate: 28%

Response Time: 18d

First Timer Success: 50%

Frequently Asked Questions

Is southleft/figma-console-mcp welcoming to first-time open-source contributors?

southleft/figma-console-mcp has a recorded first-timer success rate of 50.0%. Repositories ranked C 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 southleft/figma-console-mcp respond to incoming external pull requests in approximately 438.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 30.1 C-Rank™ score (C 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 30.1 places southleft/figma-console-mcp in the C tier.

What is the external contributor pull request merge rate for southleft/figma-console-mcp?

The external contributor pull request merge rate for southleft/figma-console-mcp is 27.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in southleft/figma-console-mcp?

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

southleft
southleft/figma-console-mcpCModerate2.1k
GitHub
Back to Explorer
southleft

southleft/figma-console-mcp

2,103
CModerate(30/100)TypeScript

Your design system as an API. Connect AI to Figma for extraction, creation, and debugging.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

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

Active TypeScript repository in southleft/figma-console-mcp with ongoing community development and issue triage.

Top PR Submission Do's

  • Ensure code complies with TypeScript style conventions
  • Keep PRs scoped and well-documented

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without context
  • Do not break existing automated test suites
Response Velocity
18 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
27.5%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
27.5%
Merge Gauge
50.0%
1st-Timer
Community Vibe26/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

This repository currently has 1 open good first issue tickets available for newcomers.

View all good first issues directly on GitHub

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 southleft/figma-console-mcp

When evaluating whether to contribute to southleft/figma-console-mcp, 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 southleft/figma-console-mcp acknowledge new external contributions in approximately 18 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 27.5% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to southleft/figma-console-mcp

01

Is southleft/figma-console-mcp welcoming to first-time open-source contributors?

southleft/figma-console-mcp has a recorded first-timer success rate of 50.0%. Repositories ranked Moderate 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 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 30.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 30.1 places southleft/figma-console-mcp in the Moderate tier.

04

What is the external contributor pull request merge rate for southleft/figma-console-mcp?

The external pull request merge rate is 27.5%. 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 southleft/figma-console-mcp?

Yes, southleft/figma-console-mcp 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 southleft/figma-console-mcp 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.