Encrypted P2P file transfer in the browser, on the desktop, and in the CLI. No accounts, no uploads, no file storage.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 84%
Response Time: 14d
First Timer Success: 100%
jannskiee/floe 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 jannskiee/floe respond to incoming external pull requests in approximately 343.9 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 56.0 places jannskiee/floe in the A tier.
The external contributor pull request merge rate for jannskiee/floe is 84.4%, based on public PR activity from non-core contributors.
jannskiee/floe does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Encrypted P2P file transfer in the browser, on the desktop, and in the CLI. No accounts, no uploads, no file storage.
Growing TypeScript project in jannskiee/floe 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/jannskiee/floe?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 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~224 hours (96% approval). Large PRs (>500 lines) take ~1651 hours (38% approval). Keep your diff compact for rapid review.
PR #282 changed the Go receiver's wire reason in the incompatible message to be written from the PEER's perspective, so peers that display it verbatim (like the browser sender at client/lib/transfer/sender.ts:232) read the correct side. The browser receiver (client/lib/transfer/receiver.ts ~line 100) still sends its LOCAL-perspective message, so the two implementations of the same wire field now follow opposite conventions, against the keep-in-sync rule in client/lib/transfer/protocol.ts's header. The fix mirrors peerCompatErrorMessage from cli/engine/transfer/protocol.go into client/lib/transfer/protocol.ts and uses it for the outgoing reason in receiver.ts. Bonus (optional): the browser sender could rebuild the message locally from the incompatible frame's pv/pvMin the way the Go sender now does, so a too-old browser is told to refresh the page rather than shown the neutral wording. Unreachable between shipped peers today (everything speaks protocol 1), so this is a safe, unit-test-d
The Settings screen's Test button (desktop/serverprobe.go) already fetches and parses the server's ICE list, but only checks that it is non-empty. A self-hosted server with no TURN relay passes the test, and the failure surfaces later: with Hide my IP enabled (relay-only), the transfer dies with a generic connection error. docs/desktop/settings.mdx documents this gap today. Suggested shape: classify the returned ICE URLs (turn:/turns: vs stun:), include a "relay available: yes/no" line in the probe result, and when Hide my IP is on and the configured server offers no TURN, fail early with a message that names the toggle. The probe result struct and its human wording live in desktop/serverprobe.go (see describeDialError for the register), with tests in serverprobe_test.go.
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 jannskiee/floe, 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 jannskiee/floe acknowledge new external contributions in approximately 14 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 84.4% were successfully merged into the primary branch.
jannskiee/floe 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 ~14 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 56.0 places jannskiee/floe in the Welcoming tier.
The external pull request merge rate is 84.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
jannskiee/floe does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for jannskiee/floe 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.