Obsidian plugin that adds elegant grid and masonry card views for Bases.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
churnish/dynamic-views has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in churnish/dynamic-views 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 8.0 places churnish/dynamic-views in the D tier.
The external contributor pull request merge rate for churnish/dynamic-views is 0.0%, based on public PR activity from non-core contributors.
churnish/dynamic-views currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Obsidian plugin that adds elegant grid and masonry card views for Bases.
Strict review standards in churnish/dynamic-views. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in churnish/dynamic-views 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/churnish/dynamic-views?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
🆙 Upscayl - #1 Free and Open Source AI Image Upscaler for Linux, MacOS and Windows.
Network-wide ads & trackers blocking DNS server
Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.
Problem After a column count change (resize), estimateUnmountedHeight() systematically overestimates unmounted card heights. When the user scrolls to these cards, the mount → remeasure → scroll compensation cycle causes a visible content shift ("reposition"). Root cause: estimateUnmountedHeight() in virtual-scroll.ts splits card height into scalableHeight (covers — scales with width) and fixedHeight (text, properties, header — treated as constant). But fixedHeight IS width-dependent: wider cards → less text wrapping → shorter actual height. The "fixed" portion isn't fixed. Measured drift: -72 to -137px per card after column increase (e.g., 2→5 cols). Scroll compensations up to -453px observed. Affects both views: Grid and Masonry share estimateUnmountedHeight(). Masonry currently animates the jump to soften it; Grid has no mitigation yet. 🤖 Generated with Claude Code
Allow to pin a property group, such that it always shows up as first — regardless of sort order.
Add an option to format a link property as a card button. Example Property link has value [Open](https://example.com). Property wikilink has value [[My note|Read]]. Both would show up as buttons Open and Read. Could even support adding Lucide, emoji, or custom SVG icons via link_icon and wikilink_icon properties. Why Pressing buttons is cooler than pressing on lame bare links. Easier on mobile too.
(The ones that are shown to the left of property names in YAML.) Ideally, support custom icons set by plugins like: Iconic Better Properties
Unsure if feasible. Ideally, would also support Quiet Outline.
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 churnish/dynamic-views, 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 churnish/dynamic-views acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
churnish/dynamic-views has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 8.0 places churnish/dynamic-views in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, churnish/dynamic-views currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for churnish/dynamic-views 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.