Self-hosted community platform Forum + Chat + Voice + P2P + Canvas + Homepage Builder. One server, one community, forever. AGPL-3.0. Discord alternative | Private Chat. | Streamer Hub
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 11%
Response Time: 2d
First Timer Success: -
Pokled/nodyx has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Pokled/nodyx respond to incoming external pull requests in approximately 52.7 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 48.0 places Pokled/nodyx in the B tier.
The external contributor pull request merge rate for Pokled/nodyx is 11.1%, based on public PR activity from non-core contributors.
Pokled/nodyx currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in Pokled/nodyx 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/Pokled/nodyx?utm_source=github&utm_medium=badge)
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 Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~34 hours (14% approval). Large PRs (>500 lines) take ~253 hours (15% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Svelte.
OpenSOHO is an OpenWISP alternative built to manage a small number OpenWRT based network devices.
The Svelte omnisite
The Appwrite website, docs and blog 🏠
Language Brazilian Portuguese / Português (Brasil) Language code pt-BR What are you planning to translate? Both Anything we should know No response
Context Nodyx should be usable with screen readers. Many interactive elements in the chat and forum views are missing proper ARIA attributes. What needs to be done Audit chat components for missing aria-label, role, and aria-live attributes Add proper labels to buttons that only have icons (send, attach, emoji picker) Add aria-live=\"polite\" to the chat message list for new message announcements Ensure forum thread list items are properly labeled Files to look at nodyx-frontend/src/lib/components/Chat*.svelte nodyx-frontend/src/routes/forum/ Skills needed HTML accessibility basics Svelte component editing No backend knowledge required
Context Nodyx provides a native installer (install.sh) and a dev docker-compose.yml, but many self-hosters prefer Docker for production deployments. What needs to be done Document how to run Nodyx in production with Docker Compose Include PostgreSQL 16 + Redis 7 + Caddy + nodyx-core + nodyx-frontend services Environment variable reference Volume mounts for persistence Add to docs/en/ and link from README Skills needed Docker / Docker Compose experience Basic understanding of reverse proxies No deep Nodyx codebase knowledge required
Context The documentation site at nodyx.dev currently only has one theme. A dark/light toggle would improve readability for users who prefer light mode. What needs to be done Add a toggle button in the documentation layout Switch between dark and light CSS themes Persist the choice in localStorage Skills needed Basic CSS / HTML / JS No backend knowledge required
Context The canvas supports multi-selection (Shift+click and lasso), but there's no Ctrl+A shortcut to select all elements at once. What needs to be done In nodyx-frontend/src/lib/components/NodyxCanvas.svelte, in the onKeydown handler: Detect Ctrl+A (or Cmd+A on Mac) Add all non-deleted, visible element IDs to selectedIds Prevent the browser default (select all text) Call render() to update the display Files to edit nodyx-frontend/src/lib/components/NodyxCanvas.svelte — onKeydown function Hint Look at how Delete key handling already iterates over selectedIds — the pattern is the same, just in reverse (adding instead of deleting).
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 Pokled/nodyx, 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 Pokled/nodyx acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 11.1% were successfully merged into the primary branch.
Pokled/nodyx has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 48.0 places Pokled/nodyx in the Solid tier.
The external pull request merge rate is 11.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Pokled/nodyx currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Pokled/nodyx 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.