A desktop image gallery with a privacy-first approach. It detects objects and clusters faces.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 65%
AOSSIE-Org/PictoPy has a recorded first-timer success rate of 64.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AOSSIE-Org/PictoPy 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.3 places AOSSIE-Org/PictoPy in the A tier.
The external contributor pull request merge rate for AOSSIE-Org/PictoPy is 64.0%, based on public PR activity from non-core contributors.
AOSSIE-Org/PictoPy currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in AOSSIE-Org/PictoPy. Maintains strict focus on technical quality and test standards.
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/AOSSIE-Org/PictoPy?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Is there an existing issue for this? I have searched the existing issues What happened? Problem: When there are no images in the album, then the add images option in the middle looks off - centered. Minor UI bug. PictoPy Right Now: PictoPy After Fix: This is not that big of a issue but it would be great to fix this css problem. Record I agree to follow this project's Code of Conduct
Summary Update the Albums detail-page layout so that it is consistent with the AI Tagging face-collection detail page. This request was made by @rohan-pandeyy in the discussion for PR #610. This issue is intentionally unassigned. Required changes Replace the current Albums detail-page back control with the outlined Back to Albums button style used by the AI Tagging face-collection detail page. Position the back button at the top left of the page content. Position the album name and description below the back button. Align Select Images and Add Images to the top-right area, on the same row as the back button. Move the image count to the right-side action area. The exact position can follow the implementation's responsive layout requirements. Keep the layout usable on mobile and desktop screens. Affected area Albums detail page UI, likely frontend/src/pages/Album/AlbumDetail.tsx and its related styles/components. Acceptance criteria The Albums detail page uses the same visual back-b
Description This issue acts as a parent tracker for ongoing documentation improvements across the project. The focus is to transition from primarily text-heavy documentation to visual, structured, and intuitive documentation that helps contributors and users quickly understand the system. Motivation While the current documentation provides useful information, much of it is heavily text-based. This makes it harder to grasp complex concepts such as system architecture, backend workflows, and data flow. Improving documentation with visuals and better structure will: Make onboarding smoother for new contributors Help users understand features and workflows faster Improve overall readability and navigation Make the project feel more polished and approachable Tasks in hand README enhancements: (PR: #1258) Add visuals such as header/banner and feature screenshots Improve structure and overall presentation Add High-Level Architecture (HLA) Backend & API Documentation API request/r
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 AOSSIE-Org/PictoPy, 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 AOSSIE-Org/PictoPy acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.0% were successfully merged into the primary branch.
AOSSIE-Org/PictoPy has a recorded first-timer success rate of 64.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.3 places AOSSIE-Org/PictoPy in the Welcoming tier.
The external pull request merge rate is 64.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AOSSIE-Org/PictoPy currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for AOSSIE-Org/PictoPy 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.