open-metadata/OpenMetadata - Open Source PR Review Scorecard

The Open Context Layer for Data and AI , OpenMetadata is the open platform for building trusted data context and business semantics for humans, AI assistants, and agents.

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

External PR Merge Rate: 73%

Response Time: 2d

First Timer Success: 48%

Frequently Asked Questions

Is open-metadata/OpenMetadata welcoming to first-time open-source contributors?

open-metadata/OpenMetadata has a recorded first-timer success rate of 47.5%. 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 open-metadata/OpenMetadata respond to incoming external pull requests in approximately 37.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 67.2 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 67.2 places open-metadata/OpenMetadata in the A tier.

What is the external contributor pull request merge rate for open-metadata/OpenMetadata?

The external contributor pull request merge rate for open-metadata/OpenMetadata is 72.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in open-metadata/OpenMetadata?

open-metadata/OpenMetadata currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

open-metadata
open-metadata/OpenMetadataA•Welcoming15.4k
GitHub
Back to Explorer
open-metadata

open-metadata/OpenMetadata

15,439
Active (30d)A•Welcoming(67/100)TypeScript

The Open Context Layer for Data and AI , OpenMetadata is the open platform for building trusted data context and business semantics for humans, AI assistants, and agents.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
6.7/10
Patience Score
7.3/10
Nitpick Rate
41%

Established TypeScript ecosystem in open-metadata/OpenMetadata. Maintains structured code review standards for external contributors.

Top PR Submission Do's

  • •Ensure code complies with TypeScript style conventions
  • •Keep PRs scoped and well-documented
  • •Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
  • •Do not mix unrelated refactors with feature work
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
72.8%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
47.5%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
80 core
Highly collaborative maintainer core
Diagnostic Health HUD
72.8%
Merge Gauge
47.5%
1st-Timer
Community Vibe45/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Affected module UI Describe the bug In Observability → Incident Manager, the Table column truncates long table names with a CSS ellipsis but gives no usable tooltip on hover, so the full name is unreachable. The cell is IncidentManagerTable.component.tsx:182-196: <Table.Cell> <Link className="tw:inline-block tw:max-w-52 tw:truncate tw:align-middle" data-testid="table-link" title={getNameFromFQN(tableFqn) ?? ref?.fullyQualifiedName} to={getEntityDetailsPath(...)}> {getNameFromFQN(tableFqn) ?? ref?.fullyQualifiedName} </Link> </Table.Cell> There are three separate defects here. 1. Wrong tooltip mechanism. The only tooltip is the bare native title attribute. Native title is browser/OS-rendered: it has a ~1s delay, is unstyled, is not shown on keyboard focus, and is suppressed entirely on touch devices. Hiding truncated content behind it fails WCAG 2.1 SC 1.4.13 (Content on Hover or Focus) and looks broken next to the rest of the app. The sibling table in the same

📅 Opened Aug 19, 2026💬 1 comment
Quality: 40/100Contribute

Right now, you can assign colors to domains in the Domains section. However, when a domain is attached to a table (or other assets), that color isn’t shown anywhere. Adding a domain and assigning a color Assigned it to an asset, same color is not showing up

📅 Opened Apr 24, 2026💬 3 comments
Quality: 5/100Contribute

**Is your feature request related to a problem? No problem, now a days only the oracle db is available, Oracle Autonomous uses MTLs to connect and we cannot set the configuration on the Web GUI solely Describe the solution you'd like Improve Oracle connector in order to support autonomous database connections Additional context We were able to set the configuration, but adding the wallet manually to the Airflow OS and setting up the TNS_ADMIN variable on OS, but it would be handy to have the setup in a Web GUI

📅 Opened Apr 16, 2026💬 11 comments
Quality: 20/100Contribute

Is your feature request related to a problem? Please describe. It would be very useful to see tag usage statistics directly in the Classification view for all tags, rather than having to click into each tag individually to check associated assets. When a classification contains many tags, it is not possible to quickly answer questions like "How many Tier1 vs Tier2 vs Tier3 assets exist?" without manually checking each tag. This makes it difficult to get an overview of tag distribution and usage at a glance. Describe the solution you'd like Add an option to display the number of assets associated with each tag directly in the main Classification view. This would allow users to quickly assess tag usage across all tags within a classification. A clear and concise description of what you want to happen. Describe alternatives you've considered offloading data off OMD to DLH and build a dashboard, but we don't want users to leave the platform Additional context v1.12.4

📅 Opened Apr 14, 2026💬 7 comments
Quality: 35/100Contribute

Affected module UI Describe the bug when customProperty lists tables, only table name is shown (and not fqn) - difficult to know which table is which if same name exists across systems. To Reproduce Screenshots or steps to reproduce Expected behavior fqn is displayed (might be smaller letters) next to table name Version: 1.12.3 as well Additional context Add any other context about the problem here.

📅 Opened Apr 1, 2026💬 16 comments
Quality: 20/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 open-metadata/OpenMetadata

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

Frequently Asked Questions - Contributing to open-metadata/OpenMetadata

01

Is open-metadata/OpenMetadata welcoming to first-time open-source contributors?

open-metadata/OpenMetadata has a recorded first-timer success rate of 47.5%. 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 67.2 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 67.2 places open-metadata/OpenMetadata in the Welcoming tier.

04

What is the external contributor pull request merge rate for open-metadata/OpenMetadata?

The external pull request merge rate is 72.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 open-metadata/OpenMetadata?

Yes, open-metadata/OpenMetadata currently has 3 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 open-metadata/OpenMetadata 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.