Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 95%
Response Time: 2d
First Timer Success: 43%
joshuaswarren/remnic has a recorded first-timer success rate of 42.9%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in joshuaswarren/remnic respond to incoming external pull requests in approximately 51.2 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 73.7 places joshuaswarren/remnic in the S tier.
The external contributor pull request merge rate for joshuaswarren/remnic is 94.6%, based on public PR activity from non-core contributors.
joshuaswarren/remnic currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.
Collaborative maintainer environment in joshuaswarren/remnic. Reviews community pull requests with focus on project quality.
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/joshuaswarren/remnic?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13: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 ~33 hours (96% approval). Large PRs (>500 lines) take ~246 hours (43% 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 TypeScript.
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
OpenLoomi is an open-source AI coworker. It connects your work tools, understands what you’re working on, and tells you what needs your attention, why it matters, and what to do next. It’s your open-source Attention Agent.
The Complete AI Development Toolkit for Claude Code — 105 skills, 36 agents, 217 hooks. Production-ready patterns for full-stack development.
Problem packages/remnic-cli/bin/remnic.cjs falls back to the TypeScript source entry when dist/index.js is absent (a source checkout, or a build that has not run yet). resolveLocalTsx() probes only the extension-less shim: const tsxCandidates = [ resolve(cwd, "../node_modules/.bin/tsx"), resolve(cwd, "../../../node_modules/.bin/tsx"), ]; On Windows, npm/pnpm generate three files in node_modules/.bin: the extension-less shim (a shell script for bash), plus tsx.cmd and tsx.ps1. Only the latter two are executable by the OS loader. existsSync matches the extension-less shim, so execFileSync(tsxCmd, ...) is handed a shell script that Windows cannot execute, and the wrapper reports Fatal: <spawn error> instead of running the CLI. Effect: on Windows, remnic <anything> fails from a source checkout until @remnic/cli is built. Published installs are unaffected because they ship dist/index.js. Expected The wrapper resolves a launchable tsx on every platform, or fails with a message that names
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 joshuaswarren/remnic, 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 joshuaswarren/remnic acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.6% were successfully merged into the primary branch.
joshuaswarren/remnic has a recorded first-timer success rate of 42.9%. Repositories ranked Elite 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 73.7 places joshuaswarren/remnic in the Elite tier.
The external pull request merge rate is 94.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, joshuaswarren/remnic currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for joshuaswarren/remnic 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.