code-input.js: An editable <textarea> that supports any syntax highlighting algorithm, for code or something else. Also, added plugins. [contribute here or on https://codeberg.org/code-input-js/code-input-js]
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 25%
Response Time: 3h
First Timer Success: 100%
WebCoder49/code-input has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WebCoder49/code-input respond to incoming external pull requests in approximately 2.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 54.8 places WebCoder49/code-input in the B tier.
The external contributor pull request merge rate for WebCoder49/code-input is 25.0%, based on public PR activity from non-core contributors.
WebCoder49/code-input currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
code-input.js: An editable <textarea> that supports any syntax highlighting algorithm, for code or something else. Also, added plugins. [contribute here or on https://codeberg.org/code-input-js/code-input-js]
Collaborative maintainer environment in WebCoder49/code-input. Reviews community pull requests with focus on project quality.
Discussions in WebCoder49/code-input 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/WebCoder49/code-input?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (31% approval). Large PRs (>500 lines) take ~12 hours (15% approval). Keep your diff compact for rapid review.
Steps to reproduce <!DOCTYPE html> <html> <body> <!--For convenience, this demo uses files from JSDelivr CDN; for more privacy and security download and host them yourself.--> <script src="https://cdn.jsdelivr.net/gh/WebCoder49/[email protected]/code-input.min.js"></script> <link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/WebCoder49/[email protected]/code-input.min.css"> <!--Import--> <script src="https://cdn.jsdelivr.net/gh/WebCoder49/[email protected]/plugins/indent.min.js"></script> <script> codeInput.registerTemplate("real", new codeInput.Template((elem) => {}, false, false, false, [new codeInput.plugins.Indent()])); </script> <button onclick="document.querySelector('code-input').setAttribute('template', 'nonexistent');">Switch to nonexistent template</button> <button onclick="document.querySelector('code-input').setAttribute('template', 'real');">Switch to real template</button>
Steps to reproduce: <!DOCTYPE html> <html> <body> <!--For convenience, this demo uses files from JSDelivr CDN; for more privacy and security download and host them yourself.--> <script src="https://cdn.jsdelivr.net/gh/WebCoder49/[email protected]/code-input.min.js"></script> <link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/WebCoder49/[email protected]/code-input.min.css"> <!--Import--> <script src="https://cdn.jsdelivr.net/gh/WebCoder49/[email protected]/plugins/indent.min.js"></script> <script> // Programatically opening the dialogs, to integrate with your user interface function goToLine() { goToLinePlugin.showPrompt(document.querySelector("code-input")); } codeInput.registerTemplate("no-indent", new codeInput.Template((elem) => { elem.style.background='lightblue'; }, false, false, false, [])); codeInput.registerTemplate("indent", new codeInput.Temp
A demo and current implementation is available in my (alpha mode, still in-development) Teclat editor project: Run the example (requires multiple windows of different browsers or devices, with the same room name in both, then clicking "Join" in both) Draft JavaScript code for the plugin Draft CSS code for the plugin, which should be made independent of Teclat's CSS variables Example usage code (the window.selectionsPlugin was instantiated as new LabelledSelections() and passed to the code-input.js template elsewhere in the rather messy code; needs to be improved, I know) The plugin itself as implemented above has no visible bugs except for accessibility: it should be usable with a screenreader; please could anyone used to a screenreader let me know what approach would work best? (Optional) announcements every time a selection changes, or announcements when you select text inside another user's selection, or an element to read out the current selections on demand? This specific plugin
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 WebCoder49/code-input, 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 WebCoder49/code-input acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.0% were successfully merged into the primary branch.
WebCoder49/code-input has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 54.8 places WebCoder49/code-input in the Solid tier.
The external pull request merge rate is 25.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WebCoder49/code-input currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for WebCoder49/code-input 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.