smp46/pingvin-share-x - Open Source PR Review Scorecard

Pingvin Share X is a secure and easy self-hosted file sharing platform.

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

External PR Merge Rate: 78%

Response Time: 5d

First Timer Success: 83%

Frequently Asked Questions

Is smp46/pingvin-share-x welcoming to first-time open-source contributors?

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

What does the 55.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 55.4 places smp46/pingvin-share-x in the A tier.

What is the external contributor pull request merge rate for smp46/pingvin-share-x?

The external contributor pull request merge rate for smp46/pingvin-share-x is 77.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in smp46/pingvin-share-x?

smp46/pingvin-share-x currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

smp46
smp46/pingvin-share-xAWelcoming345
GitHub
Back to Explorer
smp46

smp46/pingvin-share-x

345
AWelcoming(55/100)TypeScript

Pingvin Share X is a secure and easy self-hosted file sharing platform.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.0/10
Patience Score
8.2/10
Nitpick Rate
45%

Collaborative maintainer environment in smp46/pingvin-share-x. Reviews community pull requests with focus on project quality.

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
4 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
77.8%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
11 core
Highly collaborative maintainer core
Diagnostic Health HUD
77.8%
Merge Gauge
83.3%
1st-Timer
Community Vibe56/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Subject of the issue The Disk Usage widget reports the host filesystem instead of the mounted uploads filesystem when Pingvin Share X is run using Docker Desktop on macOS or Windows, even when the uploads directory is bind-mounted to a separate filesystem (e.g. an NFS share). This issue is related to #122. The Linux case has been addressed in PR #126 and correctly reports the mounted filesystem. This issue tracks the remaining behavior on Docker Desktop for macOS and Windows. Your environment Pingvin Share X: v1.21.0 macOS: Tahoe 26.5.1 Windows: Windows 11 25H2 Docker Desktop on both systems: 4.81.0 Safari: v26.5 Edge: 150.0.4078.65 macOS NFS: v3 Ubuntu WSL NFS: v4.1 WSL: v2.7.10.0 Ubuntu OS running on WSL: Ubuntu-22.04 Steps to reproduce Create a separate filesystem for uploads (e.g. an NFS share or another mounted volume). Bind mount that filesystem to /opt/app/backend/data/uploads in the Pingvin Share X Docker Compose configuration. Start Pingvin Share X using Docker Desktop. Ope

📅 Opened Jul 11, 2026💬 0 comments
Quality: 50/100Contribute

Is your feature request related to a problem? Currently, a share can only be fully managed by the user who created it. The creator of a share can edit its metadata, such as name, expiration date, password, etc. They can also manage the files inside the share by deleting existing files or adding new ones, while keeping the same public share link. Admins can see all user shares and edit share metadata as well. However, admins can only download the files contained in a share. They cannot add new files to an existing share or delete files from it. This becomes limiting in scenarios where multiple registered users need to collaboratively maintain the same share. For example, one user may create a share, but several other registered users should be able to add or remove files in that same share without creating separate share links or relying on a single owner to perform all file changes. Describe the solution or new feature you'd like I would like to request a feature that allows a share ow

📅 Opened Jul 2, 2026💬 2 comments
Quality: 90/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 smp46/pingvin-share-x

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

Frequently Asked Questions - Contributing to smp46/pingvin-share-x

01

Is smp46/pingvin-share-x welcoming to first-time open-source contributors?

smp46/pingvin-share-x has a recorded first-timer success rate of 83.3%. 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 ~4 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 55.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 55.4 places smp46/pingvin-share-x in the Welcoming tier.

04

What is the external contributor pull request merge rate for smp46/pingvin-share-x?

The external pull request merge rate is 77.8%. 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 smp46/pingvin-share-x?

Yes, smp46/pingvin-share-x currently has 2 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 smp46/pingvin-share-x 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.