OpenSignLabs/OpenSign - Open Source PR Review Scorecard

🔥 The free & Open Source DocuSign alternative

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

External PR Merge Rate: 50%

Response Time: 1h

First Timer Success: 50%

Frequently Asked Questions

Is OpenSignLabs/OpenSign welcoming to first-time open-source contributors?

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

What does the 67.5 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 67.5 places OpenSignLabs/OpenSign in the A tier.

What is the external contributor pull request merge rate for OpenSignLabs/OpenSign?

The external contributor pull request merge rate for OpenSignLabs/OpenSign is 50.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in OpenSignLabs/OpenSign?

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

OpenSignLabs
OpenSignLabs/OpenSignA•Welcoming6.8k
GitHub
Back to Explorer
OpenSignLabs

OpenSignLabs/OpenSign

6,818
InactiveA•Welcoming(68/100)Low Sample (<20 PRs)JavaScript

🔥 The free & Open Source DocuSign alternative

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

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

Established JavaScript ecosystem in OpenSignLabs/OpenSign. Maintains structured code review standards for external contributors.

Top PR Submission Do's

  • •Ensure code complies with JavaScript style conventions
  • •Keep PRs scoped and well-documented
  • •Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
  • •Do not mix unrelated refactors with feature work
Response Velocity
1 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
50.0%
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
5 core
Small core review team
Diagnostic Health HUD
50.0%
Merge Gauge
50.0%
1st-Timer
Community Vibe64/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Issue Description Every time I try to open OR download a completed document, I get a "Something went wrong, refreshing this page may solve this issue." error. I've rebooted, refreshed half a dozen times, cleared cache and cookies... I need this contract copy. Expected Behavior download or view of contract Current Behavior Nothing Steps to reproduce No response Screenshots of the issue(optional) No response Operating System [e.g. MacOS Sonoma 14.1, Windows 11] Windows 11 What browsers are you seeing the problem on? Chrome What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6] version: v2.41.2 What environment are you seeing the problem on? Production (app.opensignlabs.com) Please check the boxes that apply to this issue report. I have searched the existing issues & discussions to make sure that this is not a duplicate. Code of Conduct I agree to follow this project's Code of Conduct I have searched the existing issues & discussions to make sure that this is not a

📅 Opened Sep 21, 2026💬 1 comment
Quality: 50/100Contribute

Issue Description OpenSign Exposes a Hardcoded Parse Server Master Key Summary OpenSign publishes a Master Key in .env.local_dev: MASTER_KEY=XnAadwKxxByMr Source: .env.local_dev The backend passes MASTER_KEY directly to Parse Server: masterKey: process.env.MASTER_KEY, masterKeyIps: ['0.0.0.0/0', '::/0'], Source: index.js The published value can be supplied as X-Parse-Master-Key. A valid Parse Server Master Key bypasses application ACL and class-level permissions and provides privileged access to application data. Parse Server documents the Master Key as an override for ACL and class-level permission checks: Parse Server guide. Additional deployment defaults The Heroku application template provides another predictable Master Key: "MASTER_KEY": { "description": "A key that overrides all permissions. Keep this secret.", "value": "myMasterKey" } Source: app.json The App Engine template accepts a user-provided value but does not generate or require a strong one: MASTER_KEY: <your-master

📅 Opened Sep 8, 2026💬 0 comments
Quality: 60/100Contribute

Issue Description When first pulling and deploying OpenSign, browser access goes straight to login and does not allow me to /addadmin at all. I haven't been able to get the other fix solutions to this issue to work, so I'm hoping it's because I'm using Ubuntu Server 26.04. I'd really like to use OpenSign over DocuSeal due to having more self-hosted features avaiable. Expected Behavior Upon first access in the browser, I'm expecting to be taken to a signup page to create credentials. Current Behavior Upon first browser access, I am taken straight to the login screen. When I attempt to add /addadmin, /signup, or /register, the screen says that an admin already exists. When I check MongoDB, there is a _User DB available, but it's empty. /app and /api/app extensions do not work either. I have attempted to change the ports, URLs, leave the URLs alone — nothing seems to work. Steps to reproduce SSH into home server Install in dedicated ~/docker/opensign directory (editing the URL to the o

📅 Opened Aug 16, 2026💬 0 comments
Quality: 50/100Contribute

Issue Description No matter what I do, I cannot get this damn tool working, so I'm giving up on it. Wasted an entire day, including evening, trying to get it working. Farthest I got was the login page (as in it wasn't trying to let me create the first user) and dev console keeps saying (when loading the page): parse-DTHAhQYD.js:4 POST https://redacted.domain.com/api/app/functions/getlogobydomain 405 (Method Not Allowed) obviously changed the domain from the actual one I'm using I have been using multiple different docker methods and even kubernetes to try and get this working. And oh my god nothing works. A few times in Kubernetes I got to the point of the "create first user" page only to have a javascript error thrown once I click on the button to create the new user. I'm pretty sure the installation documentation is set up intentionally to fail. Expected Behavior No response Current Behavior No response Steps to reproduce No response Screenshots of the issue(optional) No response Op

📅 Opened Aug 1, 2026💬 0 comments
Quality: 40/100Contribute

Issue Description After promoting an existing self-hosted user to role "Admin" (UserRole field in contracts_Users), logging in triggers an "Additional Information" modal asking for Company and Job Title. Both fields are already correctly populated in MongoDB (contracts_Users.Company, contracts_Users.JobTitle), and the linked contracts_Organizations.Name / partners_Tenant.TenantName are also populated. Submitting the modal (with the fields filled in) throws uncaught exceptions in the client bundle and never proceeds - the user is completely locked out of the web GUI (login succeeds, but the app never gets past this modal). Console errors on submit: Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'message') at J (Login-CbVm_cSH.js:1:5399) at onClick (Login-CbVm_cSH.js:1) ... Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'replace') at J (Login-CbVm_cSH.js:1:5426) at onClick (Login-CbVm_cSH.js:1:12250) ... Network tab shows no f

📅 Opened Jul 21, 2026💬 0 comments
Quality: 40/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript 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 OpenSignLabs/OpenSign

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

Frequently Asked Questions - Contributing to OpenSignLabs/OpenSign

01

Is OpenSignLabs/OpenSign welcoming to first-time open-source contributors?

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

03

What does the 67.5 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 67.5 places OpenSignLabs/OpenSign in the Welcoming tier.

04

What is the external contributor pull request merge rate for OpenSignLabs/OpenSign?

The external pull request merge rate is 50.0%. 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 OpenSignLabs/OpenSign?

Yes, OpenSignLabs/OpenSign currently has 17 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 OpenSignLabs/OpenSign 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.