nextcloud/server - Open Source PR Review Scorecard

☁️ Nextcloud server, a safe home for all your data

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

External PR Merge Rate: 65%

Response Time: -

First Timer Success: 58%

Frequently Asked Questions

Is nextcloud/server welcoming to first-time open-source contributors?

nextcloud/server has a recorded first-timer success rate of 57.6%. 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 nextcloud/server 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 69.7 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 69.7 places nextcloud/server in the A tier.

What is the external contributor pull request merge rate for nextcloud/server?

The external contributor pull request merge rate for nextcloud/server is 64.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in nextcloud/server?

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

nextcloud
nextcloud/serverA•Welcoming37.1k
GitHub
Back to Explorer
nextcloud

nextcloud/server

37,093
Active (30d)A•Welcoming(70/100)PHP

☁️ Nextcloud server, a safe home for all your data

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
35%

Collaborative maintainer environment in nextcloud/server. 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
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
64.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
208 core
Highly collaborative maintainer core
Diagnostic Health HUD
64.6%
Merge Gauge
57.6%
1st-Timer
Community Vibe43/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Tip Help move this idea forward Use the 👍 reaction to show support for this feature. Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers. Subscribe to receive notifications about status changes and new comments. The occ taskprocessing:list command does not have a limit on the no. of results returned, when the list is long, it can take a while to render all the tasks with every detail about them. A new option can be added that has a default of say 10 to only fetch these many tasks from the DB and output that only. The command is defined here https://github.com/nextcloud/server/blob/7ddb822c798c2e65634b2c79dbb323711a961fa5/core/Command/TaskProcessing/ListCommand.php

📅 Opened Oct 7, 2026💬 0 comments
Quality: 50/100Contribute

Bug description When files:scan (or any code path that resolves a user's primary group via getSID()) is executed for an LDAP/AD user, a PHP warning is emitted: Error during scan: ldap_read(): Search: Invalid DN syntax The error is cosmetic (it doesn't break authentication or file access), but it registers as an error in occ files:scan output and pollutes logs. Root cause getDomainDNFromDN() in apps/user_ldap/lib/Access.php calls ldap_explode_dn($dn, 0), which returns an array that includes a 'count' key with an integer value (e.g. 4). The foreach loop does not skip non-string elements, so after finding the first dc= component, the integer 4 is appended to $domainParts: // ldap_explode_dn("cn=John Doe,ou=staff,dc=example,dc=com", 0) returns: // [0=>'cn=John Doe', 1=>'ou=staff', 2=>'dc=example', 3=>'dc=com', 'count'=>4] foreach ($allParts as $part) { if (!$dcFound && str_starts_with($part, 'dc=')) { $dcFound = true; } if ($dcFound) { $domainParts[] = $part;

📅 Opened Jun 19, 2026💬 3 comments
Quality: 80/100Contribute

Tip Help move this idea forward Use the 👍 reaction to show support for this feature. Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers. Subscribe to receive notifications about status changes and new comments. Is your feature request related to a problem? Please describe. Yes, I would like to see as an admin the groups that my apps are enabled for when using occ app:list Describe the solution you'd like When version 1.0.0 of app myapp is enabled for group mygroup, I currently see myapp: 1.0.0 under the enabled list of apps I want to see `myapp: 1.0.0 (enabled for mygroup) Describe alternatives you've considered Login and check groups via admin UI Do a database query to check groups that an app is enabled for Additional context

📅 Opened Jun 17, 2026💬 0 comments
Quality: 50/100Contribute

Tip Help move this idea forward Use the 👍 reaction to show support for this feature. Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers. Subscribe to receive notifications about status changes and new comments. Is your feature request related to a problem? Please describe. Recently i needed to search for a certain file and while i was able to find my file using the search function, i afterwards wondered, where is the file located. Somehow this information was not viewable anywhere, neither in details nor in an action in the context menu when clicking on the 3 dots of a file. Describe the solution you'd like It would be great when: the context menu has an option 'locate this file' which leads you to the specific file the details panel has a filepath header which shows the filepath where the file is located

📅 Opened May 10, 2026💬 5 comments
Quality: 30/100Contribute

⚠️ This issue respects the following points: ⚠️ This is a bug, not a question or a configuration/webserver/proxy issue. This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it). Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions. I agree to follow Nextcloud's Code of Conduct. Bug description When configuring SMB external storage via occ, using: php occ files_external:option <mount_id> password '' stores a password field as a mount option. It can then be exposed in plaintext via: php occ files_external:list --output=json as options.password. This is problematic for two reasons: It’s a potential secret-leak footgun (password in plaintext options output). It does not reliably set the SMB authentication credential where the SMB backend expects it (the correct credential setter is php occ files_external:config <mount_id> password ''). I’m proposing guardrails/warnings (or rejection) when attempt

📅 Opened Mar 10, 2026💬 3 comments
Quality: 45/100Contribute
Looking for more PHP beginner tasks?Explore PHP 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 nextcloud/server

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

Frequently Asked Questions - Contributing to nextcloud/server

01

Is nextcloud/server welcoming to first-time open-source contributors?

nextcloud/server has a recorded first-timer success rate of 57.6%. 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.7 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 69.7 places nextcloud/server in the Welcoming tier.

04

What is the external contributor pull request merge rate for nextcloud/server?

The external pull request merge rate is 64.6%. 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 nextcloud/server?

Yes, nextcloud/server currently has 5 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 nextcloud/server 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.