lokus-ai/lokus - Open Source PR Review Scorecard

Lokus - A modern, intuitive note-taking application with powerful editing capabilities

C-Rank Grade: B (Solid) - 52/100

External PR Merge Rate: 67%

Response Time: 10d

First Timer Success: 100%

Frequently Asked Questions

Is lokus-ai/lokus welcoming to first-time open-source contributors?

lokus-ai/lokus 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.

How fast can I expect code review feedback on my pull request?

Maintainers in lokus-ai/lokus respond to incoming external pull requests in approximately 233.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 52.4 C-Rank™ score (B Tier) represent?

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 52.4 places lokus-ai/lokus in the B tier.

What is the external contributor pull request merge rate for lokus-ai/lokus?

The external contributor pull request merge rate for lokus-ai/lokus is 66.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in lokus-ai/lokus?

lokus-ai/lokus currently has 20 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

lokus-ai
lokus-ai/lokusBSolid771
GitHub
Back to Explorer
lokus-ai

lokus-ai/lokus

771
BSolid(52/100)JavaScript

Lokus - A modern, intuitive note-taking application with powerful editing capabilities

Compare
Jump to:
Response Velocity
9 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
66.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
66.7%
Merge Gauge
100.0%
1st-Timer
Community Vibe57/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for lokus-ai/lokus
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/lokus-ai/lokus)](https://getmerged.abhishekco.de/lokus-ai/lokus?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Description When renaming a file in the file explorer, the filename input field opens but the text is not pre-selected. Users have to manually select the filename before typing. Steps to Reproduce Right-click on a file in the file explorer Select "Rename" from the context menu Observe: The rename input field appears but no text is selected User must manually select the filename before typing Expected Behavior When rename mode is activated: The input field should automatically select the filename excluding the extension User can immediately start typing to replace the filename The extension remains untouched unless explicitly selected Example For a file named my-notes.md: Selected text: my-notes Unselected text: .md This matches the behavior in VS Code, Finder, and Windows Explorer. Actual Behavior No text is selected, requiring manual selection before typing. Technical Notes Use input.setSelectionRange(0, filenameWithoutExtension.length) after focusing the input element.

📅 Opened Jan 15, 2026💬 2 comments
Quality: 70/100Contribute

Issue Type 🎨 UI/UX - Mobile layout or design issue Mobile Platform iOS Description [Mobile]: Make a design for iOS and Android version of the app entire layout from scratch and desktop version in mind should be similar so is familiar to user but should be adjusted to the screen and it's layout Make a figma design and drop its screenshots Files to Modify No response Proposed Solution No response Acceptance Criteria No response Difficulty None Contributor Checklist I will wrap mobile changes in isMobile() checks I will test on both mobile and desktop I will not break existing desktop functionality Code of Conduct I agree to follow this project's Code of Conduct

📅 Opened Jan 14, 2026💬 1 comment
Quality: 70/100Contribute

🟢 Good First Issue Problem MCP (Model Context Protocol) servers can't run on mobile devices. The plugin system that depends on them should be disabled or hidden. Files to Modify Look for plugin/MCP UI in: Plugin settings/preferences Plugin install dialogs Any MCP server UI Task Hide or disable MCP/plugin features on mobile with helpful messaging. Example Fix import { isDesktop } from '../platform/index.js'; // In plugin settings: {isDesktop() ? ( <PluginManager /> ) : ( <div className="p-4 text-center text-app-muted"> <p>Plugins are available on desktop only.</p> <p className="text-sm mt-2"> Download Lokus for Mac, Windows, or Linux to use plugins. </p> </div> )} Acceptance Criteria Plugin/MCP UI hidden or shows "desktop only" message No errors or crashes when accessing plugin settings Desktop plugin system unchanged ⚠️ Important: Don't break desktop plugin functionality!

📅 Opened Jan 9, 2026💬 2 comments
Quality: 70/100Contribute

🟢 Good First Issue Problem File dialogs (open() from @tauri-apps/plugin-dialog) may not work or crash on mobile. Code should check capability before calling. Files to Search/Modify Any file using: `import { open } from "@tauri-apps/plugin-dialog"` `import { save } from "@tauri-apps/plugin-dialog"` Known locations: `src/views/Launcher.jsx` (already has mobile handling) Other components that open files Task Check hasCapability('fileDialog') before calling file dialog functions. Example Fix import { hasCapability } from '../platform/index.js'; import { useToast } from '../components/Toast.jsx'; const handleOpenFile = async () => { if (!hasCapability('fileDialog')) { toast.info('File picker not available on mobile. Use recent files instead.'); return; } const file = await open({ /* options */ }); // ... handle file }; Or create mobile alternative: if (hasCapability('fileDialog')) { // Desktop: use native dialog const file = await open({ directory: true }); }

📅 Opened Jan 9, 2026💬 2 comments
Quality: 80/100Contribute

🟢 Good First Issue Problem iOS supports haptic feedback which makes touch interactions feel more responsive. Currently not utilized. File to Create/Modify src/platform/index.js or create src/utils/haptics.js Task Add a utility function to trigger haptic feedback on supported devices. Implementation // In src/platform/index.js or new file: export const triggerHaptic = (type = 'light') => { // iOS Safari haptic feedback if ('vibrate' in navigator) { const patterns = { light: 10, medium: 25, heavy: 50, success: [10, 50, 10], warning: [25, 50, 25], error: [50, 50, 50], }; navigator.vibrate(patterns[type] || patterns.light); } // Alternative: Use Tauri haptic plugin if available // try { // invoke('trigger_haptic', { type }); // } catch {} }; // Usage: import { triggerHaptic } from '../platform/index.js'; // On button press: <button onClick={() => { triggerHaptic('light'); handleAction(); }}> Action </button> //

📅 Opened Jan 9, 2026💬 1 comment
Quality: 70/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for lokus-ai/lokus

When evaluating whether to contribute to lokus-ai/lokus, 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 lokus-ai/lokus acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to lokus-ai/lokus

01

Is lokus-ai/lokus welcoming to first-time open-source contributors?

lokus-ai/lokus 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.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~9 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 52.4 C-Rank™ score represent?

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 52.4 places lokus-ai/lokus in the Solid tier.

04

What is the external contributor pull request merge rate for lokus-ai/lokus?

The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in lokus-ai/lokus?

Yes, lokus-ai/lokus currently has 20 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for lokus-ai/lokus 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.