🌐 The Internet Computer! Free, Open-Source, and Self-Hostable.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 84%
Response Time: 2d
First Timer Success: 76%
HeyPuter/puter has a recorded first-timer success rate of 76.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in HeyPuter/puter respond to incoming external pull requests in approximately 39.5 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 72.3 places HeyPuter/puter in the S tier.
The external contributor pull request merge rate for HeyPuter/puter is 84.5%, based on public PR activity from non-core contributors.
HeyPuter/puter currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
🌐 The Internet Computer! Free, Open-Source, and Self-Hostable.
Highly welcoming maintainers in HeyPuter/puter. Prompt code reviews with positive guidance for new contributors.
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/HeyPuter/puter?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~26 hours (96% approval). Large PRs (>500 lines) take ~190 hours (38% approval). Keep your diff compact for rapid review.
hi team, so i'm sharing a file from my first account (reynaldicher) to my other account (reyputer) both are logged in and i have the first one as the active session the email my 2nd account got from: clicking this link will show an empty shared folder, because i'm not on my 2nd account the question is: if i click this link should it auto switch me to my 2nd account?
I have set up puter to self host on my server, and have followed the guide to the letter for doing so behind my own reverse proxy. I have even tried working with Claude to get this working, but have found that however things are set up now are resulting in infinite redirects between puter.kylejrothfus.net and site.puter.kylejrothfus.net. Any help would be appreciated! cat config.json { "domain": "puter.kylejrothfus.net", "protocol": "https", "pub_port": 443, "env": "prod", "static_hosting_domain": "site.puter.kylejrothfus.net", "static_hosting_domain_alt": "host.puter.kylejrothfus.net", "private_app_hosting_domain": "app.puter.kylejrothfus.net", "private_app_hosting_domain_alt": "dev.puter.kylejrothfus.net", "jwt_secret": "SECRET", "jwt_secret_v2": "SECRET", "allow_v1_tokens": true, "url_signature_secret": "SECRET", "database": { "engine": "mysql", "host": "mariadb", "port": 3306, "user": "puter",
/** * Express 默认 subdomain offset=2（按 example.com 两段根域）。 * 主域 puter.bhhaihuan.com 是三段，offset=2 会把 "puter" 当成用户子域， * 从而 / → site.puter.bhhaihuan.com → 再跳回主域，形成 302 循环。 * 在 trust proxy 设置之后把 offset 调成根域标签数。 */ 'use strict'; const express = require('/opt/puter/node_modules/express'); const origSet = express.application.set; function rootLabelCount() { const fromEnv = Number(process.env.PUTER_SUBDOMAIN_OFFSET); if (Number.isInteger(fromEnv) && fromEnv >= 2) return fromEnv; try { const cfg = require('/etc/puter/config.json'); const domain = String(cfg.domain || '') .split(':')[0] .replace(/^\./, ''); const n = domain.split('.').filter(Boolean).length; if (n >= 2) return n; } catch { /* use default */ } return 3; } express.application.set = function setPatched(setting, val) { const resul
the old openai/gpt-5.3-chat model was recently discontinued, we should update it to the openai/gpt-5.6-luna which also supports web search
https://research.meta.ai/blog/introducing-muse-code-and-muse-spark-1-2 http://dev.meta.ai/
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 HeyPuter/puter, 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 HeyPuter/puter acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 84.5% were successfully merged into the primary branch.
HeyPuter/puter has a recorded first-timer success rate of 76.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 72.3 places HeyPuter/puter in the Elite tier.
The external pull request merge rate is 84.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, HeyPuter/puter 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 HeyPuter/puter 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.