Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
C-Rank Grade: S (Elite) - 83/100
External PR Merge Rate: 90%
Response Time: 10h
First Timer Success: 78%
neomjs/neo has a recorded first-timer success rate of 77.8%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in neomjs/neo respond to incoming external pull requests in approximately 9.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 82.8 places neomjs/neo in the S tier.
The external contributor pull request merge rate for neomjs/neo is 90.2%, based on public PR activity from non-core contributors.
neomjs/neo currently has 17 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
Strict review standards in neomjs/neo. Ensure PR scope matches issue requirements closely before requesting review.
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/neomjs/neo?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (96% approval). Large PRs (>500 lines) take ~46 hours (41% approval). Keep your diff compact for rapid review.
Context Eos's review of PR #19242 (review 5325187459, approved, merged at dev 6eca69b) named a reachability gap that predates that PR: VesselConversion#resolveConversion decides exit on a tri-state pointerExitedTarget — true reverts at once, false holds through a lapsed claim, null / undefined falls back to strict claim loss — but no production caller supplies it. On dev the symbol occurs only inside src/dashboard/dock/window/VesselConversion.mjs; DragCoordinator#onDragMove feeds pointerInTarget: Boolean(claimed?.zone) and TabSortZone#resolveRemoteDragTransition samples with pointerInTarget alone. Production therefore reaches exactly one of the three documented behaviours; the other two exist only in DockVesselConversion.spec.mjs ("a lapsed claim is not a departure"). The tri-state landed in fd80036 for #16497 (the film's dwell flicker: a claim expiring during a pause), on the premise that a consumer would supply exit evidence; none did. A second boundary Eos recorded, documented i
Welcome 👋 A form in Neo.mjs spaces its fields with one CSS rule. Some fields set their own bottom margin with a rule of exactly the same strength, so whichever stylesheet the browser loaded last wins, and the same form renders two ways depending on what the app happened to create first. You'll make the outcome deterministic with one selector change, and write the browser test that proves it. This is a good first issue for Hacktoberfest 2026. It needs Node.js and a clone of this repository: no Docker, no AI setup. ImportantReserved for first-time Neo.mjs contributors. The maintainer team will not claim, edit, or implement this issue through 2026-10-31. Comment here to claim it, and ask anything on this issue. Set up once: follow Set up the engine from a clone. What happens today resources/scss/src/form/Container.scss gives every direct child of a form margin-bottom: 10px through .neo-form-container > *, which has specificity (0,1,0). Two field roots set their own bottom margin at th
Context @GautamSahu028 ran the unit suite on a clean Windows 11 clone at 203de91bc2, from Git Bash (#18985 issuecomment-5830935499, the full list-reporter log attached there). The result was 50 failed, 4507 passed. The failures come from about six separate causes. This ticket covers one of them: 9 tests in 2 spec files that turn between file URLs and filesystem paths the POSIX-only way. Both cases are test-side; no engine source is involved. handoff: @GautamSahu028. They asked for this one on #19200, and it gets assigned to them as soon as they comment here, because GitHub assigns an outside contributor only after they've taken part in the issue. The Problem 1. test/playwright/unit/buildScripts/distAppAssets.spec.mjs:25: 4 failures repoRoot = path.resolve(path.dirname(new URL(import.meta.url).pathname), '../../../..') On Windows, URL.pathname is /G:/Github/neo/test/…. path.resolve reads the leading / as the current drive's root, so repoRoot becomes G:\G:\Github\neo. Observed: ENOENT:
Welcome 👋 The DevIndex grid shows a round flag next to each developer's location, from free text like "Berlin, Germany" or "San Francisco, USA". Neo.util.CountryFlags turns that text into an ISO country code and a flag URL. It has five matching steps, a few surprising edges, and no test yet. This is a good first issue for Hacktoberfest 2026. It needs Node.js and a clone of this repository: no Docker, no AI setup. ImportantReserved for first-time Neo.mjs contributors. The maintainer team will not claim, edit, or implement this issue through 2026-10-31. Comment here to claim it, and ask anything on this issue. Set up once: follow Set up the engine from a clone, including npm run bundle-browser-deps: without it the unit suite selects zero tests. Where things live Source: src/util/CountryFlags.mjs: the static methods getCountryCode(input) and getFlagUrl(nameOrCode), the aliasMap, and 243 countries New test file: test/playwright/unit/util/CountryFlags.spec.mjs Pattern to copy: test/pla
Welcome 👋 Every Neo instance gets an id like neo-button-3, and Neo.core.IdGenerator hands them out: one counter per name, a neo- prefix, and a special case for the default name. Fifteen lines, used by the whole engine, and no test yet. This is a good first issue for Hacktoberfest 2026. It needs Node.js and a clone of this repository: no Docker, no AI setup. ImportantReserved for first-time Neo.mjs contributors. The maintainer team will not claim, edit, or implement this issue through 2026-10-31. Comment here to claim it, and ask anything on this issue. Set up once: follow Set up the engine from a clone, including npm run bundle-browser-deps: without it the unit suite selects zero tests. Where things live Source: src/core/IdGenerator.mjs: getId(name), base, idCounter. It also installs Neo.getId. New test file: test/playwright/unit/core/IdGenerator.spec.mjs Pattern to copy: test/playwright/unit/util/Array.spec.mjs (the setup() call and imports) Tip: every spec in the run shares the
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 neomjs/neo, 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 neomjs/neo acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.2% were successfully merged into the primary branch.
neomjs/neo has a recorded first-timer success rate of 77.8%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 82.8 places neomjs/neo in the Elite tier.
The external pull request merge rate is 90.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, neomjs/neo currently has 17 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for neomjs/neo 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.