A Nostr Relay written in TypeScript
C-Rank Grade: S (Elite) - 78/100
External PR Merge Rate: 80%
Response Time: <1h
First Timer Success: 75%
cameri/nostream has a recorded first-timer success rate of 75.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cameri/nostream respond to incoming external pull requests in approximately 0.1 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 77.9 places cameri/nostream in the S tier.
The external contributor pull request merge rate for cameri/nostream is 80.0%, based on public PR activity from non-core contributors.
cameri/nostream currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in cameri/nostream 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/cameri/nostream?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~0 hours (36% approval). Keep your diff compact for rapid review.
Summary The app-level workers have very low or zero coverage. static-mirroring-worker.ts has 0% coverage entirely. Files to cover src/app/static-mirroring-worker.ts (0%) src/app/app.ts (20% statements, 0% branches) src/app/worker.ts (52% statements, 9% branches) src/app/maintenance-worker.ts (43% statements, 13% branches) Out of scope src/services/maintenance-service.ts — already at 100% src/services/payments-service.ts — covered by #440 All files outside src/app/ Acceptance criteria Each worker has a corresponding .spec.ts under test/unit/app/ Worker lifecycle (start, stop, error handling) covered Dependencies stubbed (DB, Redis, services) npm run cover:unit passes without regressions
Summary The following files have near-zero unit test coverage (~16% statements). Each payment processor should be tested in isolation using stubs/mocks for HTTP calls. Files to cover src/payments-processors/lnbits-payment-processor.ts (12%) src/payments-processors/lnurl-payments-processor.ts (23%) src/payments-processors/nodeless-payments-processor.ts (14%) src/payments-processors/null-payments-processor.ts (40%) src/payments-processors/opennode-payments-processor.ts (17%) src/payments-processors/zebedee-payments-processor.ts (17%) Out of scope src/services/payments-service.ts — covered by #440 Payment callback controllers — see separate issue Acceptance criteria Each processor has a corresponding .spec.ts under test/unit/payments-processors/ Happy path and error cases covered for each processor's public methods No real HTTP calls — use sinon stubs npm run cover:unit passes without regressions
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 cameri/nostream, 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 cameri/nostream acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.0% were successfully merged into the primary branch.
cameri/nostream has a recorded first-timer success rate of 75.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 77.9 places cameri/nostream in the Elite tier.
The external pull request merge rate is 80.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cameri/nostream 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 cameri/nostream 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.