NatLibFi/Skosmos - Open Source PR Review Scorecard

Thesaurus and controlled vocabulary browser using SKOS and SPARQL

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

External PR Merge Rate: 69%

Response Time: 20h

First Timer Success: 50%

Frequently Asked Questions

Is NatLibFi/Skosmos welcoming to first-time open-source contributors?

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

What does the 63.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 63.0 places NatLibFi/Skosmos in the A tier.

What is the external contributor pull request merge rate for NatLibFi/Skosmos?

The external contributor pull request merge rate for NatLibFi/Skosmos is 69.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in NatLibFi/Skosmos?

NatLibFi/Skosmos does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

NatLibFi
NatLibFi/SkosmosA•Welcoming268
GitHub
Back to Explorer
NatLibFi

NatLibFi/Skosmos

268
Active (30d)A•Welcoming(63/100)Low Sample (<20 PRs)PHP

Thesaurus and controlled vocabulary browser using SKOS and SPARQL

GitHub
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%

Growing PHP project in NatLibFi/Skosmos welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with PHP 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
20 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
69.2%
Moderate 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
5 core
Small core review team
Diagnostic Health HUD
69.2%
Merge Gauge
50.0%
1st-Timer
Community Vibe58/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for NatLibFi/Skosmos.

View all good first issues directly on GitHub

Looking for more PHP beginner tasks?Explore PHP 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 NatLibFi/Skosmos

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

Frequently Asked Questions - Contributing to NatLibFi/Skosmos

01

Is NatLibFi/Skosmos welcoming to first-time open-source contributors?

NatLibFi/Skosmos has a recorded first-timer success rate of 50.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 ~20 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 63.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 63.0 places NatLibFi/Skosmos in the Welcoming tier.

04

What is the external contributor pull request merge rate for NatLibFi/Skosmos?

The external pull request merge rate is 69.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 NatLibFi/Skosmos?

NatLibFi/Skosmos does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for NatLibFi/Skosmos 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.