IPFS Gateway implemented in Service Worker
C-Rank Grade: D (Risky) - 21/100
External PR Merge Rate: -
Response Time: 8h
First Timer Success: -
ipfs/service-worker-gateway 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 ipfs/service-worker-gateway respond to incoming external pull requests in approximately 7.6 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 20.7 places ipfs/service-worker-gateway in the D tier.
The external contributor pull request merge rate for ipfs/service-worker-gateway is 0.0%, based on public PR activity from non-core contributors.
ipfs/service-worker-gateway currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
IPFS Gateway implemented in Service Worker
Highly welcoming maintainers in ipfs/service-worker-gateway. Prompt code reviews with positive guidance for new contributors.
Discussions in ipfs/service-worker-gateway 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/ipfs/service-worker-gateway?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (81% approval). Large PRs (>500 lines) take ~37 hours (29% approval). Keep your diff compact for rapid review.
Checklist I have searched the issue tracker for existing issues. Description i have been using local agents a lot and working with https://github.com/filecoin-project/filecoin-pin.. when uploading content, my non-dumb agents have become used to sending me links to inbrowser.link/cid/ instead of other gateways.. However, some agents have tried using curl against inbrowser.link, which will obviously not work (for folks not aware, inbrowser.link is a Service worker IPFS gateway.. so, you need a browser for things to work.. curl doesn't run a full browser runtime, thankfully, when querying sites) This was particularly bad yesterday when a local Qwen3.8 tried making weird assumptions about things because querying inbrowser.link didn't give responses it expected. my proposal here is an llms.txt in addition to the existing https://inbrowser.link/robots.txt that can set folks up for success.
Checklist I have searched the issue tracker for existing issues. Description I need a option to open a file in a directory with it's direct CID Example: When open a file in a directory https://bafybeibb7eqcut4jwnxk5atcswjj7h236hv4j26yw6yalsrtcd4uafk2je.ipfs.inbrowser.link e.g. https://bafybeibb7eqcut4jwnxk5atcswjj7h236hv4j26yw6yalsrtcd4uafk2je.ipfs.inbrowser.link/Joe.jpg also option to open as: https://bafkreifpqfxttcd4irpatsbyzjps4v3ya2fspdm2lgnn5nd2otrizildn4.ipfs.inbrowser.link/
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 ipfs/service-worker-gateway, 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 ipfs/service-worker-gateway acknowledge new external contributions in approximately 7 hours. 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.
ipfs/service-worker-gateway 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 ~7 hours. 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 20.7 places ipfs/service-worker-gateway 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, ipfs/service-worker-gateway 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 ipfs/service-worker-gateway 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.