📝 Simple form & survey app for Nextcloud
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 83%
Response Time: 21h
First Timer Success: 73%
nextcloud/forms has a recorded first-timer success rate of 72.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nextcloud/forms respond to incoming external pull requests in approximately 21.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 66.1 places nextcloud/forms in the A tier.
The external contributor pull request merge rate for nextcloud/forms is 83.0%, based on public PR activity from non-core contributors.
nextcloud/forms currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in nextcloud/forms. Reviews community pull requests with focus on project quality.
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/nextcloud/forms?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 Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (96% approval). Large PRs (>500 lines) take ~101 hours (37% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in JavaScript.
No repository description available.
Transfer a QGIS project on a server, Lizmap is providing the web interface to browse it
platform engineering framework for the agentic age
Please use the 👍 reaction to show that you are affected by the same issue. Please don't comment if you have no relevant information to add! Describe the bug The expiration time for forms appears to depend on the end user's computer settings, which causes inconsistencies in the true expiry time for forms, in the case that the user's computer clock is misconfigured. To Reproduce Steps to reproduce the behavior: Set a form to expire at a certain time. Change your computer clock to be in the future. Attempt to view the form. Be unable to see the form, since your computer thinks it has expired. Expected behavior The form's expiration time should be calculated by the server, according to the server's timezone, and should not be affected by the client's (potentially incorrect) time settings. Nextcloud (please complete the following information): Nextcloud-Version: 34.0.3 Forms-Version: 5.3.5
Is your feature request related to a problem? Please describe. Currently we're using a custom textarea with markdown-it for allowing Markdown in descriptions. Describe the solution you'd like Use a default field type from nextcloud-vue library to reduce (direct) external dependencies. --> NcRichText Describe alternatives you've considered Keep everything as-is. Additional context https://nextcloud-vue-components.netlify.app/#/Components/NcRichText
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 nextcloud/forms, 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/forms acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.0% were successfully merged into the primary branch.
nextcloud/forms has a recorded first-timer success rate of 72.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 hours. 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 66.1 places nextcloud/forms in the Welcoming tier.
The external pull request merge rate is 83.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nextcloud/forms 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 nextcloud/forms 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.