Highlight and capture the web in your favorite browser. The official Web Clipper extension for Obsidian.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 13%
Response Time: 6d
First Timer Success: 50%
obsidianmd/obsidian-clipper has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in obsidianmd/obsidian-clipper respond to incoming external pull requests in approximately 138.3 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 46.1 places obsidianmd/obsidian-clipper in the B tier.
The external contributor pull request merge rate for obsidianmd/obsidian-clipper is 12.5%, based on public PR activity from non-core contributors.
obsidianmd/obsidian-clipper currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highlight and capture the web in your favorite browser. The official Web Clipper extension for Obsidian.
Active maintainer team in obsidianmd/obsidian-clipper welcoming community pull requests and bug fixes.
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/obsidianmd/obsidian-clipper?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 17:00 UTC (17: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 ~90 hours (16% approval). Large PRs (>500 lines) take ~664 hours (15% approval). Keep your diff compact for rapid review.
Title: Add Codex CLI as an interpreter provider Summary I would like to propose adding Codex CLI as an optional local interpreter provider for Obsidian Web Clipper. The motivation is to let users run prompt variables through a locally configured Codex CLI session instead of sending interpreter requests to a remote API provider. This would make Codex usable from the existing Interpreter UI in the same way as other configured models. Proposed Behavior Add a Codex CLI provider preset. Allow users to add a Codex CLI default model from the existing Interpreter settings UI. Route interpreter prompt variables through Chrome/Edge Native Messaging. Keep the existing template syntax, including prompt variables such as: {{prompt:Summarize this page in five bullet points.}} Optionally attach the current visible tab screenshot for visual/page-layout prompts. Show a native-host setup panel only when a Codex CLI provider/model is configured. Provide: OS-specific install command copy extension-ID-
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 obsidianmd/obsidian-clipper, 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 obsidianmd/obsidian-clipper acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 12.5% were successfully merged into the primary branch.
obsidianmd/obsidian-clipper has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 46.1 places obsidianmd/obsidian-clipper in the Solid tier.
The external pull request merge rate is 12.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, obsidianmd/obsidian-clipper 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 obsidianmd/obsidian-clipper 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.