AutoRAG: Now your agent can find anything in your computer. It gets smarter if you are using it frequently.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 83%
Response Time: -
First Timer Success: 75%
Marker-Inc-Korea/AutoRAG has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Marker-Inc-Korea/AutoRAG respond to incoming external pull requests in approximately 0.0 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 69.3 places Marker-Inc-Korea/AutoRAG in the A tier.
The external contributor pull request merge rate for Marker-Inc-Korea/AutoRAG is 82.9%, based on public PR activity from non-core contributors.
Marker-Inc-Korea/AutoRAG currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
AutoRAG: Now your agent can find anything in your computer. It gets smarter if you are using it frequently.
Active TypeScript repository in Marker-Inc-Korea/AutoRAG with ongoing community development and issue triage.
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/Marker-Inc-Korea/AutoRAG?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
docs: add GitHub Gists to the public datasource list Summary GitHub Gists shipped as a datasource (github-gist, #1588 / #1591). The UI catalog and the live QA harness describe it. The pages a newcomer actually reads do not. What is already true src/ui/catalog.ts has type github-gist: own-account gists, public and secret, incremental index, lexical and local semantic search. Token env falls back to the gh CLI login. The token is not stored. docs/manual-qa-datasources.md lists scripts/manual-qa/run-qa-github-gist-live.ts. README.md Supported Datasources has a GitHub row for Issues and Pull Requests only. No Gist row. docs/datasource-skills.md has no Gist section. Task Add a Gist row to the README table (alias, backend, what is stored, search modes). Keep it distinct from the Issues/PRs row. Add a short section to docs/datasource-skills.md next to the other connector skills: type, tags, token env, and the fact that semantic search stays on the local gateway. Do not copy the manual-QA s
Summary Remove the legacy StoreManifest metadata loader, manifestDir option, and the unused ## Indexed Stores system prompt section. Background src/manifest/ (StoreManifest, loadManifests) was introduced during the initial AutoRAG 2.0 monorepo migration (#1290) as a conceptual stub for describing external index stores. However, it has no actual retrieval execution logic: no retriever or search tool queries these manifests, and no CLI command exposes --manifest-dir. In current AutoRAG 2.0 architecture, external vector DBs and custom indexes belong in the standard Datasource Skill framework (DatasourceSkill, search_datasource_documents), making StoreManifest completely redundant dead code. In production/local environments, manifestDir is always unset and config.manifests is empty. Scope of Removal src/manifest/: Remove entire directory (loader.ts, types.ts, index.ts). src/agent/agent.ts: Remove manifestDir constructor option and loadManifests integration. src/agent/system-prompt.ts: R
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 Marker-Inc-Korea/AutoRAG, 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 Marker-Inc-Korea/AutoRAG acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.9% were successfully merged into the primary branch.
Marker-Inc-Korea/AutoRAG has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 69.3 places Marker-Inc-Korea/AutoRAG in the Welcoming tier.
The external pull request merge rate is 82.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Marker-Inc-Korea/AutoRAG 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 Marker-Inc-Korea/AutoRAG 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.