Image metadata library and tools
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 68%
Response Time: 5h
First Timer Success: 80%
Exiv2/exiv2 has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Exiv2/exiv2 respond to incoming external pull requests in approximately 5.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 65.8 places Exiv2/exiv2 in the A tier.
The external contributor pull request merge rate for Exiv2/exiv2 is 67.7%, based on public PR activity from non-core contributors.
Exiv2/exiv2 currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (85% critical review signals). Ensure PRs strictly follow guidelines before requesting review in Exiv2/exiv2.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/Exiv2/exiv2?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (85% approval). Large PRs (>500 lines) take ~24 hours (30% approval). Keep your diff compact for rapid review.
Describe the bug Opening a QOI image file throws exception "read access violation" Error happens on code line: Exiv2::Image::UniquePtr image = Exiv2::ImageFactory::open(filename); I have attached QOI image file I have attached screenshot of VS2022 debug session To Reproduce Steps to reproduce the behavior: Create a simple C++ program that just calls Exiv2::ImageFactory::open: Exiv2::Image::UniquePtr image = Exiv2::ImageFactory::open(filename); Debug program, step over line that opens file Read access exception is thrown Expected behavior Opening QOI file should succeed Desktop (please complete the following information): Windows 11 Exiv2 0.28.3.1, installed via NuGet package StoneSteps.Exiv2.VS2022.Static (https://www.nuget.org/packages/StoneSteps.Exiv2.VS2022.Static/0.28.3.1) Visual Studio 2022, C++ V17 Debug run in VS2022 Additional context Add any other information about the problem here.
The Metadata reference tables refers to Exif 2.3, I noticed that tag 0x8827 in Exif specification version 2.3 is called "PhotographicSensitivity", whereas in exiv2 it is called "ISOSpeedRatings", which is an old wording - as explained in the specification: "Note that this tag was referred to as “ISOSpeedRatings” in versions of this standard up to Version 2.21". The question is now if wording should be changed in exiv2. Pro: rename will follow naming in referenced specification Con: users may be irritated when the do not find ISOSpeedRatings in output of exiv2
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to Exiv2/exiv2, 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 Exiv2/exiv2 acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.7% were successfully merged into the primary branch.
Exiv2/exiv2 has a recorded first-timer success rate of 80.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 65.8 places Exiv2/exiv2 in the Welcoming tier.
The external pull request merge rate is 67.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Exiv2/exiv2 currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Exiv2/exiv2 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.