Newborn Newborn Rust RS Vue VU
↑ 38
reader hadc188/reader

「阅读3.0」（Legado）的桌面版，支持 Windows、macOS 和 Linux，使用 Rust、Tauri v2 与 Vue 3 构建。

HEALTH 79 / Stable
// solo builder// hidden gem// release machine
08-2026 · today · hadc188
★15 Share View on GitHub ↗

// readme

Reader

一个面向桌面端的本地阅读器：管理自己的书源与书架，也能阅读本地书籍、订阅 RSS，并按喜欢的方式定制阅读界面。

Reader 是「阅读3.0」（Legado）的跨平台桌面移植版，支持 Windows、macOS 和 Linux，使用 Rust、Tauri v2 与 Vue 3 构建。

项目采用纯单机设计，不需要部署服务端、数据库容器或注册账号。界面与本地核心运行在同一个桌面进程中，书架、阅读进度、缓存和配置由用户自己保存和管理。

项目源自 reader，并参考 reader-rust 进行重构。

[!IMPORTANT] 本项目不内置书源，也不提供任何书籍内容。首次启动后可导入自己拥有合法使用权的书源、本地 TXT 或 EPUB 文件。

界面预览

书架与阅读

书源与发现

统计与 RSS

项目亮点

  • 本地优先：不依赖常驻服务端，数据保存在自己的设备中。
  • 兼容阅读生态：支持 Legado 书源、RSS 源及备份数据的导入与恢复。
  • 完整书源工具：从导入、编辑、测试到登录调试都可以在桌面应用内完成。
  • 可定制阅读体验：阅读主题、字体、排版、翻页方式、背景图片与透明度均可调整。
  • 多种听书方式：支持系统语音及多种第三方语音接口格式。
  • 跨平台发布：自动构建 Windows、macOS 和 Linux 桌面安装包或便携包。

功能一览

书源、搜索与缓存

  • 导入、导出、新增、编辑和批量测试 JSON 书源
  • 远程书源订阅与一键同步更新
  • 支持 CSS 选择器、JSONPath、XPath、正则表达式及 JavaScript 解析规则
  • 多书源并行搜索，按书名和作者合并结果并显示来源数量
  • 书籍详情、目录获取、换源、章节缓存与离线阅读
  • 书源可视化编辑器、原始响应查看和分步骤规则调试
  • 书源登录预览及 Cookie 登录状态支持

阅读体验

  • 书架分组、最近阅读、书签和阅读进度记录
  • 本地 TXT、EPUB 与网络书籍阅读
  • 日间、夜间及多种阅读主题，可跟随应用外观切换
  • 字体、字号、字重、行高、段距、缩进和页面宽度调节，支持导入自定义字体
  • 滚动、左右翻页、点击翻页与自动阅读
  • 简繁转换、文字选择、内容净化与自定义替换规则
  • 阅读页右键菜单，可搜索、添加书签、换源、自动翻页和刷新 -…
↑ 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█