Esri/calcite-design-system - Open Source PR Review Scorecard

A monorepo containing the packages for Esri's Calcite Design System

C-Rank Grade: S (Elite) - 73/100

External PR Merge Rate: 75%

Response Time: 22h

First Timer Success: 84%

Frequently Asked Questions

Is Esri/calcite-design-system welcoming to first-time open-source contributors?

Esri/calcite-design-system has a recorded first-timer success rate of 84.2%. Repositories ranked S 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 Esri/calcite-design-system respond to incoming external pull requests in approximately 22.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 73.0 C-Rank™ score (S 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 73.0 places Esri/calcite-design-system in the S tier.

What is the external contributor pull request merge rate for Esri/calcite-design-system?

The external contributor pull request merge rate for Esri/calcite-design-system is 75.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Esri/calcite-design-system?

Esri/calcite-design-system currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

Esri
Esri/calcite-design-systemS•Elite373
GitHub
Back to Explorer
Esri

Esri/calcite-design-system

373
Active (30d)S•Elite(73/100)TypeScript

A monorepo containing the packages for Esri's Calcite Design System

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
35%

Highly welcoming maintainers in Esri/calcite-design-system. Prompt code reviews with positive guidance for new contributors.

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
22 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
75.1%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
46 core
Highly collaborative maintainer core
Diagnostic Health HUD
75.1%
Merge Gauge
84.2%
1st-Timer
Community Vibe69/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

monday.com sync: #11323057002 Check existing issues I have checked for existing issues to avoid duplicates and reviewed the Accessibility page for guidance. Which Component Notice Summary The open property of calcite-notice doesn't properly hide content when it is false or missing. (Sorry if this is a duplicate, it was hard to search for this specific problem) Actual Behavior When the calcite-notice component's open property is false, the content is only hidden visually and is still available to assistive technology. Expected Behavior When the notice is closed/not open, I would expect it to be fully hidden and not just visually hidden. Reproduction Sample https://developers.arcgis.com/calcite-design-system/components/notice Reproduction Steps Open the component sample in CodePen. Remove the open property to set it to false. Observe that the calcite-notice content is only hidden visually. It can still be read with a screen reader and it is not hidden from the accessibility tree. Re

📅 Opened Feb 20, 2026💬 2 comments
Quality: 45/100Contribute

monday.com sync: #11038671226 Check existing issues I have checked for existing issues to avoid duplicates Which Component Tab Description Proposed: allow the user to adjust the gap between tab-titles (e.g. by exposing --calcite-internal-tab-nav-gap?) Acceptance Criteria let the user reduce the gap – or reduce the gap according to width – to enhance compact layouts Relevant Info No response Example Use Case We use calcite-tabs in the header of "Scene tools" in Scene Viewer. This is a compact, fixed-width UI, with 5 icon-only tab-titles. The whole calcite-tab-nav is 248px wide. With the gap between tab-titles being fixed to --calcite-internal-tab-nav-gap the width of each tab is limited to 25px Reducing the gap would make the buttons more easy to click E.g. Priority impact impact - p3 - not time sensitive Calcite package @esri/calcite-components @esri/calcite-components-react @esri/calcite-design-tokens @esri/calcite-ui-icons @esri/eslint-plugin-calcite-components Es

📅 Opened Jan 19, 2026💬 4 comments
Quality: 30/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 Esri/calcite-design-system

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

Frequently Asked Questions - Contributing to Esri/calcite-design-system

01

Is Esri/calcite-design-system welcoming to first-time open-source contributors?

Esri/calcite-design-system has a recorded first-timer success rate of 84.2%. Repositories ranked Elite 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 ~22 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 73.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 73.0 places Esri/calcite-design-system in the Elite tier.

04

What is the external contributor pull request merge rate for Esri/calcite-design-system?

The external pull request merge rate is 75.1%. 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 Esri/calcite-design-system?

Yes, Esri/calcite-design-system currently has 2 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 Esri/calcite-design-system 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.