dsh.so
EN
English中文
@yeweiliang7063/dsh-tcm avatar

@yeweiliang7063/dsh-tcm

《npm 上的 dsh-tcm 1.3.0 是旧版、已废弃，请勿安装 》！！！！！！！！！！ DSH 中医预设「岐黄经方（学习版）」2.2.0：先给一行大白话结论，再按经方思路七段讲清辨证定位、治则治法、方名与加减方向、推荐穴位、配伍禁忌、药典用量警示、调护与就医提示；危险动作打 🚨⚠️ 标签，古文翻成白话。只讲思路，不给剂量，不出处方笺。

PluginKnowledge
Verification
L3 · Install spec
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: No L4/L5 install test yetInstall verification details →

Data as of (UTC)

What it does

《npm 上的 dsh-tcm 1.3.0 是旧版、已废弃，请勿安装 》！！！！！！！！！！ DSH 中医预设「岐黄经方（学习版）」2.2.0：先给一行大白话结论，再按经方思路七段讲清辨证定位、治则治法、方名与加减方向、推荐穴位、配伍禁忌、药典用量警示、调护与就医提示；危险动作打 🚨⚠️ 标签，古文翻成白话。只讲思路，不给剂量，不出处方笺。

Installation

dsh plugin --profile web add github:yeweiliang7063/dsh-tcm#v2.2.0
tested artifact v2.2.0

Install method: GitHub · install spec verified (L3)

Verification & Compatibility

Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.

External credentials (plugin-level): none detected

Declared DSH compatibilityfrom package.json · peerDependencies
package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v2.2.0github2026-11-14

https://github.com/yeweiliang7063/dsh-tcm

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-tcm-2.svg)](https://www.dsh.so/artifact/dsh-tcm-2/?ref=badge)`

dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.

Security Report

Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.

dsh-tcm-2Automated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low
vet findings0 critical·0 high
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
Version binding
plugin versionv2.2.2dsh manifest
scanned versionv2.2.2git2026-11-14
current versionv2.2.2same version
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (3)
  • warningchildProcess · code-execinstall.mjs:216

    const r = spawnSync(process.execPath, [path.join(HERE, 'verify-preset.mjs')], {

  • warningfsWrite · filesinstall.mjs:63

    fs.writeFileSync(file, JSON.stringify(data, null, 2) + '\n', 'utf8')

  • warningchildProcess · code-execverify-preset.mjs:168

    const r = spawnSync(process.execPath, ['--input-type=module', '-e',

2dynamic auditmodel reads redacted source context · never executes plugin code

not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.

Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.

Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.

Activity

Last commit 2026-11-14 · activity: Active

• Repo created: 2026-11-14

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/yeweiliang7063/dsh-tcm

Frequently asked questions

What is @yeweiliang7063/dsh-tcm?

@yeweiliang7063/dsh-tcm is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.

Is dsh.so or this plugin page official?

dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.

How do I install @yeweiliang7063/dsh-tcm?

Run dsh plugin --profile web add github:yeweiliang7063/dsh-tcm#v2.2.2 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.

How does the security scan relate to a manual audit?

Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.

How fresh is the data on this page?

The data on this page is as of 2026-11-14 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.

Was this page helpful?