certimate-go/certimate - Open Source PR Review Scorecard

An open-source and free self-hosted SSL certificates ACME tool, automates the full-cycle of issuance, deployment, renewal, and monitoring visually. 完全开源免费的自托管 SSL 证书 ACME 工具,申请、部署、续期、监控全流程自动化可视化,支持各大主流云厂商。

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

External PR Merge Rate: 78%

Response Time: 1d

First Timer Success: 50%

Frequently Asked Questions

Is certimate-go/certimate welcoming to first-time open-source contributors?

certimate-go/certimate 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 certimate-go/certimate respond to incoming external pull requests in approximately 31.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 67.3 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.3 places certimate-go/certimate in the A tier.

What is the external contributor pull request merge rate for certimate-go/certimate?

The external contributor pull request merge rate for certimate-go/certimate is 78.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in certimate-go/certimate?

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

certimate-go
certimate-go/certimateA•Welcoming9.4k
GitHub
Back to Explorer
certimate-go

certimate-go/certimate

9,358
Active (30d)A•Welcoming(67/100)Go

An open-source and free self-hosted SSL certificates ACME tool, automates the full-cycle of issuance, deployment, renewal, and monitoring visually. 完全开源免费的自托管 SSL 证书 ACME 工具,申请、部署、续期、监控全流程自动化可视化,支持各大主流云厂商。

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.7/10
Patience Score
8.2/10
Nitpick Rate
30%

Collaborative maintainer environment in certimate-go/certimate. 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
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
78.3%
High acceptance rate for external PRs

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
17 core
Highly collaborative maintainer core
Diagnostic Health HUD
78.3%
Merge Gauge
50.0%
1st-Timer
Community Vibe52/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

Release Version / 软件版本 V0.4.35 Description / 缺陷描述 Steps to reproduce / 复现步骤 登录首页仪表盘提示404 Logs / 日志 Details # Paste logs here / 请在此粘贴日志 Miscellaneous / 其他 No response Contribution / 贡献代码 I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!

📅 Opened Oct 14, 2026💬 1 comment
Quality: 60/100Contribute

Description / 功能描述 Can you add luadns to the dns providers available on the gui ? Motivation / 请求动机 need to configure cert request. Miscellaneous / 其他 No response Contribution / 贡献代码 I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!

📅 Opened Oct 10, 2026💬 1 comment
Quality: 60/100Contribute

Release Version / 软件版本 v0.4.30 Description / 缺陷描述 1.创建监控工作流中会有多个分支,当证书过期或者当前域名不存在证书的时候会申请证书 2.证书申请成功后会执行后续部署步骤 3.部署步骤失败后,当第二天自动触发工作流后会重复申请证书不会校验现有的证书库中是否有大于网站现在使用的证书有效期的新证书,而且执行盲目重新申请 Steps to reproduce / 复现步骤 1.创建一个工作流,最开始的步骤为监控域名证书有效期 2.下来是并行操作,当有效期大于设置的阈值停止操作,小于则申请证书然后替换新证书 3.当替换步骤失败后,没有即使认为干预,工作流因为设置的定时任务再次被触发后重复申请证书,这时证书库中会存在多个相同域名的证书。 Logs / 日志 Details # Paste logs here / 请在此粘贴日志 Miscellaneous / 其他 1.这个问题存在好几个版本了,我不

📅 Opened Oct 8, 2026💬 8 comments
Quality: 75/100Contribute

Release Version / 软件版本 0.4.28 Description / 缺陷描述 部署到腾讯云edgeone makers失败 一、部署到edgeone国际版 提示“failed to execute sdk request 'teo.makers.DescribePagesZoneCustomDomains': sdkerr: api error: code='109', message='The Token usage region is incorrect.'” 二、部署到edgeone国内版 1.如果设置“根据证书自动匹配” 提示“[2026-07-22 12:11:17] api request 'teo.makers.DescribePagesZoneCustomDomains' [2026-07-22 12:11:17] could not deploy certificate [2026-07-22 12:11:17] could not find any domains matched by certificate” 2.如果精准设置一个域名 提示“workflow engine panic: runtime error: index out of range [0] with length 0” (此处错误不显示在日志框,如图,日志框里面根本不提示任何错误) Steps to reproduce / 复现步骤 1.设置流程,部署到腾讯云edgeone国内版和国际版; 2.如果是国际版,填写接口端点,如果是国内版,留空; 3.国际版和国

📅 Opened Jul 22, 2026💬 19 comments
Quality: 80/100Contribute
Looking for more Go beginner tasks?Explore Go 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 certimate-go/certimate

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

Frequently Asked Questions - Contributing to certimate-go/certimate

01

Is certimate-go/certimate welcoming to first-time open-source contributors?

certimate-go/certimate 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 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 67.3 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.3 places certimate-go/certimate in the Welcoming tier.

04

What is the external contributor pull request merge rate for certimate-go/certimate?

The external pull request merge rate is 78.3%. 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 certimate-go/certimate?

Yes, certimate-go/certimate 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 certimate-go/certimate 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.