maziyarpanahi/openmed - Open Source PR Review Scorecard

Local-first healthcare AI: clinical NER & HIPAA PII de-identification that runs 100% on-device. 2,200+ medical models, 21 languages, Apple MLX + Python, no cloud, no patient data leaving your network. Apache-2.0

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

External PR Merge Rate: 74%

Response Time: 2d

First Timer Success: 75%

Frequently Asked Questions

Is maziyarpanahi/openmed welcoming to first-time open-source contributors?

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

What does the 64.4 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 64.4 places maziyarpanahi/openmed in the A tier.

What is the external contributor pull request merge rate for maziyarpanahi/openmed?

The external contributor pull request merge rate for maziyarpanahi/openmed is 74.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in maziyarpanahi/openmed?

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

maziyarpanahi
maziyarpanahi/openmedAWelcoming5.1k
GitHub
Back to Explorer
maziyarpanahi

maziyarpanahi/openmed

5,074
AWelcoming(64/100)Python

Local-first healthcare AI: clinical NER & HIPAA PII de-identification that runs 100% on-device. 2,200+ medical models, 21 languages, Apple MLX + Python, no cloud, no patient data leaving your network. Apache-2.0

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 maziyarpanahi/openmed. 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
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
74.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
15 core
Highly collaborative maintainer core
Diagnostic Health HUD
74.2%
Merge Gauge
75.0%
1st-Timer
Community Vibe52/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Summary Private-training rounds need explicit enrollment, update-submission, aggregation, and evaluation windows. Ambiguous or overlapping deadlines make lifecycle state and air-gapped participation nondeterministic. Scope Define an immutable UTC schedule with strictly ordered phase boundaries, optional maximum durations, and deterministic serialization. Resolve the active or next phase from a caller-injected timestamp without reading the system clock. Acceptance criteria Before-start, exact-boundary, active-phase, and after-finish cases resolve predictably for every phase. Naive timestamps, non-UTC offsets, reversed or equal boundaries, booleans, and excessive durations fail with field-only errors. The schedule contains no site identity, patient count, local metric, or network endpoint. .venv/bin/python -m pytest tests/unit/training/test_federated_schedule.py -q passes. Out of scope Network coordination, client notification, retries, or selecting the round lifecycle state. Extend

📅 Opened Aug 29, 2026💬 0 comments
Quality: 90/100Contribute

Summary A client capability envelope and an immutable round manifest are useful only if compatibility is checked before enrollment. The comparison must explain incompatibility without exposing client identity, exact hardware inventory, or local data characteristics. Scope Compare protocol versions, training backend, model and adapter format, quantization support, declared resource class, deterministic-kernel support, privacy mechanism, and secure-aggregation mode. Return compatible, review-required, or incompatible with stable field-level reason codes and a metadata-only deterministic report. Acceptance criteria Exact match, supported version range, insufficient resources, unsupported privacy mode, adapter mismatch, and unknown requirement cases have table-driven tests. Unknown mandatory requirements fail closed; optional capability differences are distinguished from hard incompatibilities. Reports exclude client IDs, site names, hardware serials, paths, endpoints, patient counts, l

📅 Opened Aug 29, 2026💬 0 comments
Quality: 90/100Contribute

Summary Several multimodal modules compute SHA-256 independently, and callers need a shared streaming helper that does not load large PDFs, images, DICOM objects, or audio files into memory. Scope Hash bytes and binary streams in bounded chunks, returning the SHA-256 digest and byte count with an optional hard maximum. Preserve a seekable stream's position, never close caller-owned streams, and keep errors free of paths, filenames, and byte content. Acceptance criteria Bytes, seekable streams, non-seekable streams, empty input, and multi-chunk input match hashlib.sha256 reference digests. Exceeding the configured maximum fails before unbounded reading and reports only the limit category and numeric counts. Tests verify position restoration for seekable streams, no implicit close, and bounded read request sizes. .venv/bin/python -m pytest tests/unit/multimodal/test_digest.py -q passes. Out of scope Cryptographic signatures, content-addressed storage, or opening filesystem paths. Ma

📅 Opened Aug 29, 2026💬 0 comments
Quality: 90/100Contribute

Summary The new asset manifest, media-type detector, modality profiles, resource limits, and streaming digest checks need one pre-decode entry point. Without a common report, each future VLM, OCR, DICOM, waveform, and audio provider will assemble different safety behavior. Scope Orchestrate manifest validation, declared-versus-detected media type, modality-specific fields, digest matching, and resource limits into a single accept-or-abstain report. Return deterministic findings, reason codes, schema versions, numeric metadata, and digests only; never open a heavy decoder or copy source content into the report. Acceptance criteria Synthetic happy-path examples for image, PDF, DICOM, and audio are accepted with byte-stable JSON. Media mismatch, malformed manifest, digest mismatch, insufficient metadata, and every resource-limit class produce ordered fail-closed findings. A sentinel test proves filenames, paths, OCR text, transcripts, DICOM values, credentials, and raw prefix bytes do

📅 Opened Aug 29, 2026💬 0 comments
Quality: 90/100Contribute

Summary A generic asset manifest can be structurally valid while still omitting the metadata needed to preflight its declared modality. Image dimensions, PDF page counts, DICOM frame geometry, and audio duration need explicit cross-field rules. Scope Add versioned image, PDF, DICOM, and audio manifest profiles that declare required, optional, and inapplicable metadata fields. Validate a privacy-safe asset manifest into deterministic field-only findings without opening or decoding the asset. Acceptance criteria Image width/height, PDF page count, DICOM frame count plus dimensions, and audio duration requirements have table-driven valid and invalid tests. Inapplicable fields, missing required fields, zero values, booleans, and non-finite numeric values produce stable categorical findings. Results contain only field names and reason codes, never source paths, embedded metadata, or media content. .venv/bin/python -m pytest tests/unit/multimodal/test_manifest_profiles.py -q passes. Out

📅 Opened Aug 29, 2026💬 2 comments
Quality: 90/100Contribute
Looking for more Python beginner tasks?Explore Python 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 maziyarpanahi/openmed

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

Frequently Asked Questions - Contributing to maziyarpanahi/openmed

01

Is maziyarpanahi/openmed welcoming to first-time open-source contributors?

maziyarpanahi/openmed has a recorded first-timer success rate of 75.0%. 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 64.4 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 64.4 places maziyarpanahi/openmed in the Welcoming tier.

04

What is the external contributor pull request merge rate for maziyarpanahi/openmed?

The external pull request merge rate is 74.2%. 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 maziyarpanahi/openmed?

Yes, maziyarpanahi/openmed currently has 34 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 maziyarpanahi/openmed 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.