📄 Easily create your resume with Markdown on VSCode / Typora / Obsidian
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
BingyanStudio/LapisCV 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 BingyanStudio/LapisCV 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 BingyanStudio/LapisCV in the D tier.
The external contributor pull request merge rate for BingyanStudio/LapisCV is 0.0%, based on public PR activity from non-core contributors.
BingyanStudio/LapisCV currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in BingyanStudio/LapisCV. Reviews community pull requests with focus on project quality.
Discussions in BingyanStudio/LapisCV 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/BingyanStudio/LapisCV?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
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.
问题描述 感谢作者制作了这个优秀的模板！但在使用过程中发现一个影响体验的问题： lapis-cv.css和lapis-cv-serif.css 文件中将多个字体（JetBrainsMono、SourceHanSansCN、SourceHanSerifCN）以 Base64 形式直接内嵌，导致该 CSS 文件体积达到46.7MB。 带来的影响 无法正常编辑：50MB 的单文件无法用常规文本编辑器（VS Code、记事本等）打开进行自定义修改，会严重卡顿甚至崩溃 首次加载慢：Obsidian 需要完整下载 50MB 的 CSS 才能渲染页面 内存占用高：Base64 解码后字体占用额外约 100MB 内存 PDF 导出变慢：每次导出都需要解码 Base64，增加不必要的开销 建议改进方案 将 @font-face 中的 Base64 数据提取出来，保存为独立的 .ttf 或 .woff2 字体文件，放在 fonts/ 目录下，CSS 中改为相对路径引用： @font-face { font-family: 'JetBrainsMono'; src: url('fonts/JetBrainsMono.woff2') format('woff2'); } 改进
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 BingyanStudio/LapisCV, 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 BingyanStudio/LapisCV 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.
BingyanStudio/LapisCV 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 BingyanStudio/LapisCV 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, BingyanStudio/LapisCV 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 BingyanStudio/LapisCV 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.