PaaS (Platform as a Service) on Docker 🐳 or k8s ☸
C-Rank Grade: D (Risky) - 16/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
traPtitech/NeoShowcase has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in traPtitech/NeoShowcase 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 15.7 places traPtitech/NeoShowcase in the D tier.
The external contributor pull request merge rate for traPtitech/NeoShowcase is 0.0%, based on public PR activity from non-core contributors.
traPtitech/NeoShowcase currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in traPtitech/NeoShowcase. Reviews community pull requests with focus on project quality.
Discussions in traPtitech/NeoShowcase focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/traPtitech/NeoShowcase?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
問題の説明 キューにある（QUEUED の）ビルドは、ユーザーがキャンセルできない。 ダッシュボードの Cancel Build ボタンは、BUILDING のときにしか表示されない（dashboard/src/components/templates/build/BuildStatusTable.tsx） API の CancelBuild は QUEUED のビルドに対して呼んでも何もしないが、成功を返す。controller の ControllerBuilderService.CancelBuild は、そのビルドを実行中の builder 接続に CANCEL_BUILD を送るだけで、QUEUED のビルドにはまだ builder 接続がないため送り先がない QUEUED のビルドが CANCELLED になるのは、同じアプリに新しいコミットや設定のビルドが積まれたときだけ（pkg/usecase/cdservice/service.go）。builder が空かないと、不要なビルドがキューに残り続ける。 新機能の説明 QUEUED のビルドもキャンセルできるようにする。 gateway の CancelBuild（pkg/usecase/apiserver/a
バグの概要 website がないアプリでも自動シャットダウンを有効にできる。 有効にすると、アプリが起動しないまま、起動させる手段もなくなる。 Sablier がアプリを起動するきっかけは、Traefik の Sablier middleware を通る HTTP リクエストだけである。 website がないアプリには IngressRoute も middleware も作られないので、停止したアプリを起こす経路がない。 k8s backend: デプロイ時点で StatefulSet の replicas が 0 になる（pkg/infrastructure/backend/k8simpl/synchronize_runtime.go）ので、一度も起動しない docker backend: Sablier に停止されたあと、再び起動することがない 再現手順 runtime アプリを website なしで作成する（bot や worker など） 自動シャットダウンを有効にしてデプロイする 期待する動作 website がないアプリは、自動シャットダウンの設定にかかわらず常時起
バグの概要 タイトル通り 再現手順 ユーザーAがアプリ1を作成する ユーザーAがアプリ1にhttps://example.comのurlを登録する ユーザーAがアプリ2を作成する ユーザーAがアプリ2にhttps://example.com/path/overlayのurlを登録する ユーザーB（アプリ2のオーナーだがアプリ1のオーナーではない）がアプリ2の設定（ブランチ等）を変更する 期待する動作 設定変更が通る 実際の動作 website conflictというエラーが出る 再現環境 No response スクリーンショット No response 関連情報 No response
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 traPtitech/NeoShowcase, 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 traPtitech/NeoShowcase acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
traPtitech/NeoShowcase has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 15.7 places traPtitech/NeoShowcase in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, traPtitech/NeoShowcase currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for traPtitech/NeoShowcase 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.