CloudFlare free temp domain email 免费收发 临时域名邮箱 支持附件 IMAP SMTP TelegramBot
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 77%
Response Time: -
First Timer Success: 100%
dreamhunter2333/cloudflare_temp_email has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dreamhunter2333/cloudflare_temp_email 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.
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 63.4 places dreamhunter2333/cloudflare_temp_email in the A tier.
The external contributor pull request merge rate for dreamhunter2333/cloudflare_temp_email is 76.9%, based on public PR activity from non-core contributors.
dreamhunter2333/cloudflare_temp_email currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
CloudFlare free temp domain email 免费收发 临时域名邮箱 支持附件 IMAP SMTP TelegramBot
Active maintainer team in dreamhunter2333/cloudflare_temp_email welcoming community pull requests and bug fixes.
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/dreamhunter2333/cloudflare_temp_email?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (35% approval). Keep your diff compact for rapid review.
请描述您的 Feature 描述您想要的解决方案 描述您考虑过的替代方案 附加上下文
请描述您的 Feature 需求： 根据收到邮件的From、Subject或内容进行过滤后再调用webhook或推送。 比如uptimerobot的服务up/down的通知要怎样过滤状态然后调用webhook再进行服务的启动？ 描述您想要的解决方案 最好可以通过工作流来实现。可以参考下 https://www.upti.my/ 的workflows实现。使用接收做为触发事件然后使用过滤节点筛选是否符合条件，然后再执行相应的动作。 大部分网站都支持邮件做为推送接收方式。可以考虑加入更多的uptime类功能。
请描述您的 Feature 每次有新邮件通过webhook发送到企业微信群中，若有附件，还需要专门打开邮箱软件，很麻烦。 能否提供webhook变量，是这些附件的链接。 描述您想要的解决方案 能否把邮件里的附件存到cloudfare中，然后转为链接，在webhook中提供固定前几个附件的变量，这些变量是用来引用附件的链接。 简化：可以在webhook中，只提供附件里的第一个文件链接变量吗，这些附件全部都是图片形式。 描述您考虑过的替代方案 无。 附加上下文 同类功能： https://github.com/Hk-Gosuto/ChatGPT-Next-Web-LangChain 这个软件是把ai绘制的图片存到cloudfare中，以链接形式打开图片。
请描述您的 Feature 账号设置里面的这几个配置我看一半天没看懂是干嘛的，文档好像也没有写。目前如果想屏蔽某个发件人邮箱的邮件，是把黑名单配置到【接收邮件地址屏蔽关键词】这里面吗，最后达到的效果是收不到这个邮件吗，可以增加一个垃圾箱，然后将屏蔽的邮件地址发来的邮件投入垃圾箱不 描述您想要的解决方案 将屏蔽的邮件地址发来的邮件投入垃圾箱
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 dreamhunter2333/cloudflare_temp_email, 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 dreamhunter2333/cloudflare_temp_email acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.9% were successfully merged into the primary branch.
dreamhunter2333/cloudflare_temp_email has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 63.4 places dreamhunter2333/cloudflare_temp_email in the Welcoming tier.
The external pull request merge rate is 76.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dreamhunter2333/cloudflare_temp_email currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for dreamhunter2333/cloudflare_temp_email 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.