ScriptCat, a browser extension that can execute userscript; 脚本猫，一个可以执行用户脚本的浏览器扩展
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 72%
Response Time: 2d
First Timer Success: 50%
scriptscat/scriptcat has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in scriptscat/scriptcat respond to incoming external pull requests in approximately 41.7 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 52.9 places scriptscat/scriptcat in the B tier.
The external contributor pull request merge rate for scriptscat/scriptcat is 71.6%, based on public PR activity from non-core contributors.
scriptscat/scriptcat does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
ScriptCat, a browser extension that can execute userscript; 脚本猫，一个可以执行用户脚本的浏览器扩展
Rigorous architecture standards (83% critical review signals). Ensure PRs strictly follow guidelines before requesting review in scriptscat/scriptcat.
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/scriptscat/scriptcat?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~27 hours (90% approval). Large PRs (>500 lines) take ~200 hours (32% approval). Keep your diff compact for rapid review.
提交前检查 我已经搜索过现有 issues，并尽量用最新 stable 或 beta 版本确认问题仍然存在 问题描述 实际发生了什么： Edge Dev 154 上 ScriptCat 管理的全部用户脚本（10 个）静默失效——扩展弹窗仍显示「当前页运行脚本 (1/1)」（静态 URL 匹配），但页面内任何脚本都未执行，无报错、无日志、无提示。重启浏览器、重载扩展均无法恢复。 期望： 脚本正常注入执行。 根因（已定位并验证）： registerUserscripts() 的早退守卫只校验了 chrome.userScripts 侧的注册，未校验 chrome.scripting 侧： // src/app/service/service_worker/runtime.ts L1077-1088 if (runtimeGlobal.registerState === RuntimeRegisterCode.REGISTER_DONE) { const res = await chrome.userScripts.getScripts({ ids: ["scriptcat-inject"] }); if (res.length === 1) { return; // ← 早退时未检查 chrome.scripting.getRegisteredContentScripts() } ... } 我机器上实测的状态
环境 扩展：脚本猫 Beta 备份来源：脚本猫导出的 sync.zip 复现步骤 从备份 ZIP 导入脚本； 关闭并重新打开浏览器（或再次导入同一备份）。 现象 导入后脚本「来源」列为「本地脚本」（无安装源），无法接收版本更新； 多次导入同一备份会产生大量重复脚本（实测：33 个脚本经多次导入叠加后出现 122 条记录，需手动逐条去重）。 根因（推测） 导入逻辑 import.js 对 .meta.json 无处理（源码中 .meta.json 出现 0 次），备份格式未形成闭环； 判重仅按「名称 + 命名空间」且为静默覆盖，重复导入会叠加而非幂等更新。 影响 备份恢复脆弱，无法保证幂等； 用户脚本失去安装源，无法自动更新。 建议 导入时补全 / 保留 @updateURL / @installURL，使「本地脚本」可附带安装源； 导入增加幂等处理（按 UUID 或 name+namespace 去重，避免重复叠加）； 支持 .meta.
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 scriptscat/scriptcat, 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 scriptscat/scriptcat acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.6% were successfully merged into the primary branch.
scriptscat/scriptcat has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 52.9 places scriptscat/scriptcat in the Solid tier.
The external pull request merge rate is 71.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
scriptscat/scriptcat does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for scriptscat/scriptcat 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.