High performance self-hosted photo and video management solution.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 58%
Response Time: -
First Timer Success: 34%
immich-app/immich has a recorded first-timer success rate of 33.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in immich-app/immich respond to incoming external pull requests in approximately 0.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 63.5 places immich-app/immich in the A tier.
The external contributor pull request merge rate for immich-app/immich is 58.1%, based on public PR activity from non-core contributors.
immich-app/immich currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
High performance self-hosted photo and video management solution.
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in immich-app/immich.
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/immich-app/immich?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (73% approval). Large PRs (>500 lines) take ~115 hours (26% approval). Keep your diff compact for rapid review.
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. Yes The bug Noticed while uploading the files to server, tried to add a description and it just dropped the text after the uploaded files count (that is in album) is changed _20260923_123609.webm The OS that Immich Server is running on Debian 13 Version of Immich Server V3.2.0 Version of Immich Mobile App Platform with the issue Server Web Mobile Device make and model Windows 11 25H2, Firefox 156.0 Your docker-compose.yml content services: immich-server: image: ghcr.io/immich-app/immich-server:release volumes: - /mnt/immich-cold:/usr/src/app/upload/upload - /home/arsen/photos/thumbs:/usr/src/app/upload/thumbs - /home/arsen/photos/encoded-video:/usr/src/app/upload/encoded-video - /home/arsen/photos/profile:/usr/src/app/upload/profile - /home/arsen/photos/backups:/usr/src/app/upload/backups -
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. Yes The bug First, I want to thank you for this project! Now, I don't have to use f*** Google Photos! The bug: you can zoom in photos endlessly, like you see in the video. VID-20260913-WA0000.mp4 The OS that Immich Server is running on Sorry don't know Version of Immich Server 3.1.0 Version of Immich Mobile App 3.2.0 Platform with the issue Server Web Mobile Device make and model Fairphone 6 android 16 Your docker-compose.yml content Don't know Your .env content Don't know Reproduction steps 1.open a photo 2.start zooming 3. ... Relevant log output Additional information No response
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. Yes The bug Reproduction Steps Open the Immich Web App. Go to the Memories section. Open a Memory. Observe the date shown in the Memory title/header. Scroll through the assets/photos contained in that Memory. Compare the dates of the individual assets with the date shown in the Memory title. Expected Behavior The date displayed in the Memory title should correspond to the actual date of the assets contained in the Memory. For an “On This Day” style Memory, the Memory date should represent the day on which those photos were actually taken. Actual Behavior The Memory title displays a date one day behind of the dates shown for the assets inside the Memory. For example, if the assets are dated September 11, the Memory title may display September 10. This makes the Memory appear to represent the wrong day. The OS that Immich Server is running on docker Version of Immich Server v3.
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. Yes The bug With the third party solution I use to provide mobile daily memory notifications, it defaults to linking to either the newest, oldest, or a random day in past years, then ending there once that day's photos are done. If I want to view the rest of the previous years' memories, I have to exit to the Immich homepage and tap on the memories at the top, which will then automatically continue to the next year once a year's memories are done. I tried to fix this by modifying the link used in the notification service to deep-link://immich://memory rather than deep-link://immich://memory?id=<selected memory ID>, but that results in just opening to the Immich homepage when tapping the notification. This looks to be because of this line, where a nullish memory ID defaults to '', but then buildMemoryDeepLink explicitly checks for null, resulting in it looking for memory ID '', and
The Immich API and database should store null instead of empty strings. Columns where this is happening: album.description (#30123) asset_exif.description person.name person.thumbnailPath session.deviceType session.deviceOS user.password (#30223) user.profileImagePath user.oauthId user.name
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 immich-app/immich, 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 immich-app/immich acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.1% were successfully merged into the primary branch.
immich-app/immich has a recorded first-timer success rate of 33.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 63.5 places immich-app/immich in the Welcoming tier.
The external pull request merge rate is 58.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, immich-app/immich 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 immich-app/immich 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.