The malleable knowledge base for you and your team. Powered by Markdown and Lua.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 54%
Response Time: -
First Timer Success: 53%
silverbulletmd/silverbullet has a recorded first-timer success rate of 53.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in silverbulletmd/silverbullet 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 67.0 places silverbulletmd/silverbullet in the A tier.
The external contributor pull request merge rate for silverbulletmd/silverbullet is 53.6%, based on public PR activity from non-core contributors.
silverbulletmd/silverbullet currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The malleable knowledge base for you and your team. Powered by Markdown and Lua.
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in silverbulletmd/silverbullet.
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/silverbulletmd/silverbullet?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (67% approval). Large PRs (>500 lines) take ~115 hours (24% approval). Keep your diff compact for rapid review.
Attribute style rules are not applied on the toc with edge 2.5.3-cabe886813ade60b2e32da12259656d4d3a69cd1-2026-03-26T16-54-38Z: this was the case with edge 2.5.3-c9434a02f17deb049d0bdad274d9dc5a89c8eb5c-2026-03-25T14-38-31Z: Note - The space between the text and the attribute is not preserved whatever the version of edge: Excerpt fromspace-style: /* FINI / .sb-attribute[data-FINI]> .sb-frontmatter.sb-meta:is(:has(+ .sb-frontmatter:not(.sb-meta):not(.sb-attribute-name))) { display: none; / ":" n'est pas affiché / } .sb-attribute[data-FINI] > .sb-frontmatter.sb-attribute-name { display: none; / le nom de l'attribut n'est pas affiché / } .sb-attribute[data-FINI] > .sb-frontmatter.sb-attribute-value { background: #20F420; /vert clair/ color: white; } / OUVERT / .sb-attribute[data-OUVERT]> .sb-frontmatter.sb-meta:is(:has(+ .sb-frontmatter:not(.sb-meta):not(.sb-attribute-name))) { display: none; / ":" n'est pas affiché / } .sb-attribute[data-OUVERT] > .sb-frontmatter.sb-attribute-n
-- lists files that comply with a path and are referenced from links even if the page does not exist. function listfiles(path) local pages = {} for linked_page in query[[from tags.link select _.toPage order by _.toPage]] do if type(linked_page) == 'string' then if linked_page.startsWith(path) then pages['[['..linked_page..']]'] = linked_page end end end return table.keys(pages) end - ## Namespaces - ### Area - ${listfiles('sb/commands')} When line with - ### Area indented then function listfiles output has first two characters truncated. Note. The function works perfectly in other pages however the truncation of the function output appears to be specifically related to the heading above the function line getting indented
ideally have a helm chart to be able to install the image into a kubernetes cluster.
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 silverbulletmd/silverbullet, 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 silverbulletmd/silverbullet acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.6% were successfully merged into the primary branch.
silverbulletmd/silverbullet has a recorded first-timer success rate of 53.3%. 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 67.0 places silverbulletmd/silverbullet in the Welcoming tier.
The external pull request merge rate is 53.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, silverbulletmd/silverbullet currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for silverbulletmd/silverbullet 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.