Skybridge is a full-stack TypeScript framework for MCP Apps and ChatGPT Apps. Type-safe. React-powered. Platform-agnostic.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 81%
Response Time: -
First Timer Success: 80%
alpic-ai/skybridge has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in alpic-ai/skybridge 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 62.7 places alpic-ai/skybridge in the A tier.
The external contributor pull request merge rate for alpic-ai/skybridge is 80.6%, based on public PR activity from non-core contributors.
alpic-ai/skybridge currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Skybridge is a full-stack TypeScript framework for MCP Apps and ChatGPT Apps. Type-safe. React-powered. Platform-agnostic.
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in alpic-ai/skybridge.
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/alpic-ai/skybridge?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 (96% approval). Large PRs (>500 lines) take ~115 hours (36% approval). Keep your diff compact for rapid review.
The devtools preview doesn't reproduce the background a real host (ChatGPT, Claude…) paints behind the view's iframe, so the rendered result doesn't match what ships. Two symptoms: Fullscreen — the background shows as white regardless of the view's own background. E.g. a view with a lavender (light) background renders white in fullscreen. Inline / PiP — the background is always effectively transparent. Switching the simulated theme to Dark updates the view's CSS, but the area behind stays transparent, so white text/buttons sit on the devtools' grey panel and become unreadable. Impact: hard to iterate on UI and judge how a view will look inside the final host. Likely area: the preview container in packages/devtools/src/components/layout/tool-panel/view/index.tsx — fullscreen forces bg-background (devtools chrome) behind the iframe, while inline/PiP applies no surface color at all. The container should paint the simulated host surface for the current theme behind the iframe in al
For example if the host (or forwarded host) is capitals.skybridge.tech, the widgetDomain value should be skybridge.tech This solves the issue where the punch out button default location (the widgetDomain) still points on a URL with a web server. Related to #255 (comment)
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 alpic-ai/skybridge, 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 alpic-ai/skybridge acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.6% were successfully merged into the primary branch.
alpic-ai/skybridge has a recorded first-timer success rate of 80.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 62.7 places alpic-ai/skybridge in the Welcoming tier.
The external pull request merge rate is 80.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, alpic-ai/skybridge 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 alpic-ai/skybridge 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.