xhongc/music-tag-web - Open Source PR Review Scorecard

音乐标签编辑器,可编辑本地音乐文件的元数据, 音乐刮削。(Editable local music file metadata.)

C-Rank Grade: D (Risky) - 8/100

External PR Merge Rate: -

Response Time: -

First Timer Success: -

Frequently Asked Questions

Is xhongc/music-tag-web welcoming to first-time open-source contributors?

xhongc/music-tag-web 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.

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

Maintainers in xhongc/music-tag-web 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.

What does the 7.5 C-Rank™ score (D 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 7.5 places xhongc/music-tag-web in the D tier.

What is the external contributor pull request merge rate for xhongc/music-tag-web?

The external contributor pull request merge rate for xhongc/music-tag-web is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in xhongc/music-tag-web?

xhongc/music-tag-web currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

xhongc
xhongc/music-tag-webD•Risky6.1k
GitHub
Back to Explorer
xhongc

xhongc/music-tag-web

6,114
InactiveD•Risky(8/100)Low Sample (<20 PRs)Python

音乐标签编辑器,可编辑本地音乐文件的元数据, 音乐刮削。(Editable local music file metadata.)

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in xhongc/music-tag-web. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in xhongc/music-tag-web focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

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

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

Active Good First Issues (3)

View on GitHub

【Bug问题】: /rest/getPlaylist 返回的 songCount / duration 恒为 0,第三方 Subsonic 客户端显示错误 环境说明 版本:music-tag-web V2(docker latest) 接口:Subsonic 兼容端点 /rest/getPlaylist(f=json) 现象 getPlaylist 返回的 playlist.songCount 和 playlist.duration 永远是 0,但 entry 数组本身是正常的、包含了歌单全部曲目。实测一个 223 首的歌单: "songCount": 0, "duration": 0, "entry": [ ...223 项... ] 任意歌单都复现,与歌单内容无关。 影响 songCount / duration 是 Subsonic 规范里 playlist 的标准字段,第三方 Subsonic 客户端(Symfonium、DSub、play:Sub 等)常用它们展示曲目数和总时长,现在会全部显示为 0。 期望 按 entry 实际内容填充这两个字段(songCount = entry 数量,duration = 曲目时长之和)。 辛苦作者看看,感谢!

📅 Opened Sep 8, 2026💬 0 comments
Quality: 50/100Contribute

环境说明 版本:music-tag-web V2(docker latest) 访问方式:桌面浏览器 页面:音乐收藏 → 风格 → 风格详情页 现象 风格详情页顶部介绍文案里的数量占位符没有被替换,直接把模板变量原样显示出来了: 收拢 {albumCount} 张专辑和 {trackCount} 首歌曲,适合按同一种气质连续聆听。 右侧统计卡里的实际数字(专辑/歌曲/已载入)是正常的,只有这句介绍文案漏了插值。所有风格都是这样(Pop、Anime、Classical 都复现)。 期望 渲染时把 {albumCount}、{trackCount} 替换成该风格的实际数量,例如"收拢 301 张专辑和 1395 首歌曲……"。看起来是文案模板做了参数化但渲染时忘了传参。 辛苦作者看看,感谢!

📅 Opened Sep 7, 2026💬 1 comment
Quality: 75/100Contribute

环境说明 版本:music-tag-web V2(docker latest) 访问方式:桌面浏览器 现象 在"正在播放"大屏页面,如果当前歌曲标题较长(古典乐、OST 场景很常见),标题会以很大的字号渲染,几行下来直接溢出左侧卡片区域,把下方的专辑封面和黑胶动画都盖住了,观感比较滑稽。短标题(两三个字)时显示是正常的,猜测是标题字号固定、没有针对超长文本做自适应。 例如播放《Symphony No. 1 in C Major, Op. 21: I. Adagio molto - Allegro con brio》时,标题换行后溢出卡片并遮挡封面。 期望 标题过长时能自适应处理,例如: 标题超过一定行数后自动缩小字号,或超长部分省略号截断; 或者超长标题做跑马灯滚动; 保证标题区域和封面/黑胶展示区域互不遮挡。 古典乐和影视原声类曲库长标题很常见,这个问题会比较频繁地暴露。辛苦作者看看,感谢!

📅 Opened Sep 7, 2026💬 0 comments
Quality: 35/100Contribute
Looking for more Python beginner tasks?Explore Python 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 xhongc/music-tag-web

When evaluating whether to contribute to xhongc/music-tag-web, 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 xhongc/music-tag-web 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.

Frequently Asked Questions - Contributing to xhongc/music-tag-web

01

Is xhongc/music-tag-web welcoming to first-time open-source contributors?

xhongc/music-tag-web 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.

02

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

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

03

What does the 7.5 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 7.5 places xhongc/music-tag-web in the Risky tier.

04

What is the external contributor pull request merge rate for xhongc/music-tag-web?

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.

05

Are there beginner Good First Issues open in xhongc/music-tag-web?

Yes, xhongc/music-tag-web currently has 3 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 xhongc/music-tag-web 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.