// readme

🪪 香港入境处预约配额监控

实时追踪香港入境事务处换领身份证预约配额，新名额放出时 飞书群 + 飞书私聊 自动通知。

📱 方式一：加入飞书群（推荐）

机器人自动推送配额变化，消息秒达，加群即用，无需任何配置。

📖 群信息 & 加群方式（多群方案，群满自动分流）

💬 方式二：飞书私聊订阅

如果不想加群，也可以按日期过滤，仅接收你关注日期的通知：

  1. 私聊机器人「HKID放号自动监测」（发送任意消息即可触发）
  2. 机器人会回复交互卡片，支持：
    • 📅 订阅特定日期 — 只关注你预约的那天
    • 🔔 订阅全部日期 — 所有放号都通知
    • 📊 查看 / 修改 / 取消订阅
  3. 也可以直接回复日期一键订阅，例如 08/15, 08/20-08/25

支持三种过滤模式：

  • 📅 按日期 — 只看特定日期，不限办事处
  • 🏢 按办事处 — 只看特定办事处，不限日期
  • 🎯 按日期+办事处 — 精确匹配

💡 机器人私聊有 1-2 秒延迟，着急的话推荐进群。

🖥 看板

🖥 quota-monitor 看板

  • 📊 实时查看全港各办事处预约配额状态
  • 📈 放号规律热力图，可视化各时段放号频次
  • 📖 附电话预约办理教程
  • 🔧 内置管理后台，支持订阅者管理、统计概览、双通道群发

📨 通知流程

检测到新配额放出时，按以下顺序推送：

群聊广播（多群并行）→ 私聊 DM（并行，仅推送给匹配日期的订阅者）

飞书群和私聊几乎同时到达。

🔒 隐私与安全

  • 飞书用户数据使用 AES-256-GCM 加密存储，仓库中不可读
  • 仅读取入境处公开发布的配额数据
  • ⚠️ 免责声明：本系统为第三方开源工具，非香港入境事务处官方服务，请以官网信息为准

📄 License

MIT © Deng Zheyi

⚠️ 本开源项目仅供学习交流使用，请勿用于任何商业盈利目的。

🙏 鸣谢

  • 数据来源：[香港入境事务处 —…
↑ 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█