9001/copyparty - Open Source PR Review Scorecard

Portable file server with accelerated resumable uploads, dedup, WebDAV, SFTP, FTP, TFTP, zeroconf, media indexer, thumbnails++ all in one file

C-Rank Grade: S (Elite) - 72/100

External PR Merge Rate: 67%

Response Time: -

First Timer Success: 50%

Frequently Asked Questions

Is 9001/copyparty welcoming to first-time open-source contributors?

9001/copyparty has a recorded first-timer success rate of 50.0%. Repositories ranked S 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 9001/copyparty 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.

What does the 71.8 C-Rank™ score (S 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 71.8 places 9001/copyparty in the S tier.

What is the external contributor pull request merge rate for 9001/copyparty?

The external contributor pull request merge rate for 9001/copyparty is 66.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in 9001/copyparty?

9001/copyparty currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

9001
9001/copypartyS•Elite46.9k
GitHub
Back to Explorer
9001

9001/copyparty

46,948
InactiveS•Elite(72/100)Low Sample (<20 PRs)Python

Portable file server with accelerated resumable uploads, dedup, WebDAV, SFTP, FTP, TFTP, zeroconf, media indexer, thumbnails++ all in one file

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in 9001/copyparty.

Top PR Submission Do's

  • •Verify all existing package test suites run cleanly
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
66.7%
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
27 core
Highly collaborative maintainer core
Diagnostic Health HUD
66.7%
Merge Gauge
50.0%
1st-Timer
Community Vibe42/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

Describe the bug As seen here, some settings are set by default, and notably a pretty important one, hist, that sets the cache dir location. When the user change the settings, the values get overriden, thus breaks thumbnail generation because it then tries to write thumbnails into a .hist folder at the root of the volume, which copyparty needs write access to do so (not the case by default). Additionally, the module sets some values, such as externalCacheDir or externalStateDir. Not only the user can't override these values, this also means that a user changing the location of services.copyparty.settings.hist wouldn't automatically add it to the BindPaths of the systemd service, so copyparty wouldn't have access to the folder. There are probably more issues, this is what I quickly found after trying to find out why my thumbnails wouldn't generate. To Reproduce Set services.copyparty.settings to anything, thumbnail generation breaks. Set services.copyparty.settings.hist to anything othe

📅 Opened Sep 3, 2026💬 1 comment
Quality: 90/100Contribute

collabora online (cool/code/coolwsd) seems to work thanks to #1495 however editing with onlyoffice is currently not possible #1495 (comment) mentioned they were able to open a document read-only, but I'm not even getting to that point; when I try to create a new document with the "new textfile" feature in the copyparty ui, for example with the filename some.docx then I see onlyoffice successfully initializes the empty document in the copyparty volume, then onlyoffice asks for the properties of the document, and then nothing more happens; onlyoffice never asks for the contents of the document, and the onlyoffice ui is stuck in a "loading" state, as if the document has not yet been transferred into the editor, however there is zero explanation why in either the copyparty or onlyoffice logs perhaps onlyoffice doesn't like something about the wopi response sent from copyparty? a complicating factor is that this whole feature (the wopi integration) is something i do not care for, something

📅 Opened Jul 24, 2026💬 8 comments
Quality: 80/100Contribute

Describe the bug When using the NixOS module to configure copyparty including a space in a volume's path results in the SystemD service to fail. To Reproduce Create a folder with a space in the name Add a volume using the created folder to the Copyparty using the NixOS module Expected behavior The service to start and the volume with a space to be bound. Example "/TV Shows" = { path = "/mnt/drive-a/TV Shows"; access = { A = [ "cody" ]; }; }; Causes: activating the configuration... setting up /etc... reloading user units for cody... restarting sysinit-reactivation.target the following new units were started: NetworkManager-dispatcher.service warning: the following units failed: copyparty.service × copyparty.service - http file sharing hub Loaded: loaded (/etc/systemd/system/copyparty.service; enabled; preset: ignored) Active: failed (Result: exit-code) since Tue 2026-04-07 23:27:26 MST; 1s ago Duration: 1d 1h 16min 3.051s Invocation: 93e1c5027cd04ac5a423b9eb1b

📅 Opened Apr 8, 2026💬 3 comments
Quality: 45/100Contribute

is your feature request related to a problem? Please describe. Multiple projects like No-Intro, Myrient, Redump, MAME, TOSEC, ... use the ".dat"-file format from RomVault and DATVault for checksumming and integrity testing. This also allows people to build their collection with files from different sources while ensuring they've the same file. List of indexing projects that use this format: https://wiki.romvault.com/doku.php?id=supported_dats Describe the idea / solution you'd like Would it be possible to implement support for these dat files in a way that allows: others to basically get a copy of the index (in this dat format) as if it was a regular file (e.g. in a /dats folder). to import/upload dat files to serve as index (manage the DATRoot) for files that should be there but aren't yet, e.g. if they're uploaded they will automatically appear under this file tree (aka be automatically sorted). to automatically update dat files in the background (when given via URL similar to how t

📅 Opened Mar 29, 2026💬 1 comment
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python 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 9001/copyparty

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

Frequently Asked Questions - Contributing to 9001/copyparty

01

Is 9001/copyparty welcoming to first-time open-source contributors?

9001/copyparty has a recorded first-timer success rate of 50.0%. Repositories ranked Elite 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.8 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 71.8 places 9001/copyparty in the Elite tier.

04

What is the external contributor pull request merge rate for 9001/copyparty?

The external pull request merge rate is 66.7%. 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 9001/copyparty?

Yes, 9001/copyparty currently has 4 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 9001/copyparty 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.