// readme

DSH Plugin Hub

面向 DeepSeek Harness 社区的插件目录、安装证据索引与轻量安全筛查站。
Discover community plugins with real GitHub metadata, manifest evidence, and transparent risk signals.

· · ·

项目简介

DeepSeek Harness 的插件生态增长很快，但仓库描述、安装命令和真实权限边界经常散落在不同位置。DSH Plugin Hub 将这些公开证据汇总成一个可搜索目录，帮助用户在安装前先确认：

  • 项目是否真的声明了 dsh.bundle、dsh.plugin、dsh.profile 或 dsh.client；
  • 安装命令是否绑定到完成静态检查的不可变 Git commit；
  • 仓库是否活跃、是否有许可证和锁文件；
  • 是否存在生命周期脚本、网络访问、文件写入、凭据读取或动态代码执行信号；
  • 当前结果来自自动发现、社区精选，还是离线快照。

本站是独立社区项目，与 DeepSeek 官方没有隶属关系。

核心能力

能力说明
真实插件数据合并社区精选列表、GitHub topic:dsh-plugin 元数据和仓库根目录 manifest。
岚叔严选收录巡检中经过源码、版本、安装路径和安全边界核验，并明确判断“现在值得试”的插件。每条严选绑定审核 commit。
自动收录Cloudflare Cron 每 12 小时发现新仓库、同步严选列表，候选进入 Queue 并行检查，结果写入 D1。
安装证据只有在同一 Git commit 上完成 manifest 与入口源码检查后，才展示锁定 commit 的安装命令。
插件护照每个 仓库 + commit + 扫描器版本 都有不可变证据页、原始 JSON 与检查文件清单。
版本变更雷达自动比较依赖、生命周期脚本、外联域名、能力信号、维护者和 manifest 变化。
轻量筛查检查许可证、锁文件、生命周期脚本和有限源码信号，并公开展示发现项。
插件浏览支持搜索、分类、证据筛选、排序、卡片/列表视图和本地收藏。
双语与主题支持中文、English、浅色和深色界面。
开放数据提供动态 JSON API、运行状态接口和构建时静态快照。
访问热度D1…
↑ 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█