Quiet Quiet JavaScript JS HTML HT
35
Chrome-Renamer zhangxuyuan20251443-coder/Chrome-Renamer

Privacy-first Chrome extension to rename Google, YouTube, and Chrome labels locally. 本地网页品牌改名与自定义新标签页扩展。

https://zhangxuyuan20251443-coder.github.io/Chrome-Renamer/ ↗
HEALTH 80 / Healthy
// solo builder// help wanted// hidden gem browser-extensionchrome-extensioncustomizationgooglelocal-firstmanifest-v3new-tabprivacyproductivityyoutube

// readme

Chrome Renamer

Rename visible Google, YouTube, and Chrome labels—locally.

在本机自定义 Google、YouTube 和 Chrome 页面中的可见名称。

A privacy-first Manifest V3 Chrome extension for personalized brand labels and a custom new tab page.

· · ·

⭐ If Chrome Renamer is useful, use GitHub’s Star button to save it and help others discover it.
如果它对你有帮助,欢迎点击 GitHub 页面顶部的 Star 收藏并帮助更多人发现它。

中文简介

Chrome Renamer 是一款本地运行的 Chrome 扩展,可自定义网页中可见的 Google、YouTube 和 Chrome 品牌名称,并提供个性化新标签页。

  • 名称设置只保存在本机 Chrome 扩展存储中
  • 支持动态加载的网页内容和常见无障碍标签
  • 可对当前网站一键暂停或恢复名称替换
  • 邮箱地址、网址和域名保持原样,不会被改名
  • 不需要账号,不包含分析、广告或开发者服务器

下载 Chrome Renamer 1.1.2 · 查看 30 秒安装步骤

扩展只能修改普通 HTTP/HTTPS 网页中的内容以及自己的新标签页,不能修改 Chrome 地址栏、菜单、设置页或操作系统界面。

Make the web feel like yours

Chrome Renamer replaces supported visible brand labels on ordinary web pages and keeps the same names on its custom new tab page.

BeforeAfter—you choose the names
Google…
The Undervalued Score +

How much a project earns versus how much attention it actually gets. Above 50 means the work is outrunning its audience. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.

score  = signal / reach

signal = 0.25·commit_velocity   // commits in last 90 days (cap 30)
       + 0.20·contributor_work  // unique authors × velocity (cap 100)
       + 0.20·issue_resolution  // closed ÷ total issues
       + 0.20·fork_ratio        // forks ÷ stars (proxy for real usage)
       + 0.10·release_cadence   // releases in 90 days (cap 3)
       + age_bonus              // +0 to +0.30 after 6 months
       + homepage_bonus         // +0.05 if homepage is set

reach  = log₁₀(stars + watchers + 10)
The Health Score +

Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

health = 0.35·recency       // days since last commit (90d decay)
       + 0.25·cadence       // commit rhythm consistency
       + 0.20·issue_health  // closed ÷ total issues
       + 0.20·pr_health     // merged ÷ total PRs
Health bands +

The colour and label on every card come straight from the health score.

Healthy   80 – 100   active, responsive, regular releases
Stable    60 – 79    maintained, steady, no alarms
Quiet     40 – 59    slowing down — watch this one
At Risk    0 – 39    going dark · candidate for rescue
// Tags — what each label means +

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

solo_builder      one person holds > 80% of commits (last 180d)
needs_contributors has open "help wanted" or "good first issue" labels
hidden_gem        < 100 stars · active in last 3 months · documented
legacy_hero       repo > 5 years old · committed this year
fork_magnet       forks/stars > 0.5 · used as template or dependency
release_machine   5+ releases in the last 90 days
under_pressure    > 10 open issues · ≤ 2 contributors · health ≥ 60
community_watch   watchers > stars · devs tracking before the public
community_hub     GitHub Discussions enabled · > 20 discussions
funded            maintainer has active funding channel
Why rank against stars at all? +

Stars are an outcome, not effort. A project with 8 stars and daily commits is doing more interesting work than one coasting on 8k. We measure the building, then divide by the attention already received — so the genuinely undervalued rise to the top.

// stars   = lagging indicator
// commits = leading indicator
// we rank by the leading one