Open-source workspace for professional document AI: reviewable agent edits, source-linked work, three-way document merges, and an extensible plugin runtime. Starting with legal work.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: -
AI-WorkDeck/aiworkdeck 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 AI-WorkDeck/aiworkdeck 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 49.4 places AI-WorkDeck/aiworkdeck in the B tier.
The external contributor pull request merge rate for AI-WorkDeck/aiworkdeck is 100.0%, based on public PR activity from non-core contributors.
AI-WorkDeck/aiworkdeck currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in AI-WorkDeck/aiworkdeck. Reviews community pull requests with focus on project quality.
Discussions in AI-WorkDeck/aiworkdeck 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/AI-WorkDeck/aiworkdeck?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05: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 (45% approval). Keep your diff compact for rapid review.
Why Follow frontend/src/locales/CONVENTIONS.md. zh-CN / en-US namespace files must have identical key sets (npm run check:locales). Task From frontend/, run npm run check:locales (or node scripts/check-locale-parity.mjs). Pick one failing namespace file pair (e.g. editor.js or whichever fails). Add the missing keys on the other side; translate via glossary.md (add glossary rows first if a term is new). Re-run check until that namespace (ideally the whole suite) passes. Acceptance PR touches at most one namespace pair (+ glossary if needed) check:locales green for that namespace No emoji; EN uses English punctuation only Claim Comment「认领」below before starting. Please read .github/CONTRIBUTING.md and sign legal/CLA.md. Not in scope Large i18n refactors; extracting new hard-coded UI strings (separate issue).
Why i18n / contributor on-ramp. examples/hello-web-plugin/README.md is Chinese-only; international contributors bounce. Task Either: Add a clear English section to the same README, or Add README.en.md and link it from the top of the Chinese README Keep technical commands identical; do not invent APIs. Acceptance English content covers install paths, demos (awd.ready, files, toast, storage, evidence.list), and sandbox boundaries Links to PLUGIN_SPEC / SDK still work Not in scope Rewriting the plugin code or SDK.
Why examples/hello-declarative-plugin/ has manifest + l10n + template but no README. hello-web-plugin already has a strong Chinese README to mirror. Task Add examples/hello-declarative-plugin/README.md (CN + EN) covering: What a declarative plugin is (no Java) How l10n %name% keys map to l10n/zh-CN.json / en-US.json How to install (same plugin dirs as hello-web-plugin) What template / styleProfile / settings it contributes Link to docs/plugin-guide.md or PLUGIN_SPEC.md Acceptance README present and accurate against current manifest Install path table included Not in scope Changing plugin behavior.
Why Parent (pay track core stays with maintainers): #66. Issue already describes a Quick check; newcomers need a copy-paste runbook with expected screenshots placeholders. Task Add docs/dev-notes/lowa-ui-locale-quickcheck.md (or under docs/ if dev-notes not yet created) containing: Install / open latest desktop release Open any docx in embedded editor Navigate to Language Settings → User Interface What “lists zh-CN” vs “English only” means for options 1 vs 2 in #66 Where to paste findings (comment on #66) No product code changes. Acceptance Runbook merged Linked from a comment on #66 Not in scope Implementing zh-CN langpack or custom toolbar (#66 implementation).
Why Parent: #15. Warm-up for docs hygiene without boiling the ocean. Task Create docs/dev-notes/. Move one clearly historical/internal file (suggested candidates: docs/AUDIT_2026-08-20_REMAINING.md, docs/HANDOFF_EDITOR_REVIEW_2026-09-11.md, or docs/DESENSITIZATION_REVIEW_2026-09-10.md). Leave a 5-line stub at the old path pointing to the new location (so old links do not 404). Update docs/README.md if it already exists; otherwise mention the move in the PR. Acceptance File lives under docs/dev-notes/ Stub at old path No broken relative links you introduced (fix any in-repo links to that filename) Not in scope Bulk-moving all internal docs.
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 AI-WorkDeck/aiworkdeck, 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 AI-WorkDeck/aiworkdeck acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
AI-WorkDeck/aiworkdeck 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 ~-. 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 49.4 places AI-WorkDeck/aiworkdeck in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AI-WorkDeck/aiworkdeck currently has 11 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for AI-WorkDeck/aiworkdeck 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.