deepseek harness plugins · verified 2026-11-21 · comparison v1.0.0

memory-eternal vs dsh-vision-router: memory-eternal has the edge.

memory-eternal is the better fit when you use Claude Code or Cursor or MCP. memory-eternal lists them; dsh-vision-router does not. Both list DeepSeek Harness. The registry does not report documentation, license, declared access and more for at least one listing. Verified against the HOL registry on 2026-11-21.

  • Trust 88 vs 89
  • Scans agree
  • Claude Code, Cursor, DeepSeek Harness, MCP
  • MIT · updated 2026-11-21
memory-eternal · trust
88/100
dsh-vision-router · trust
89/100
At a glance
License: MIT / Not declared · Plugin type: Plugin / Plugin · Works with: Claude Code, Cursor, DeepSeek Harness, MCP / DeepSeek Harness · Owner verified: Yes / Yes · Security scan: Needs review (83/100, 17 findings) / Needs review (83/100, 15 findings) · Last updated: 2026-11-21 / 2026-11-19 · Install commands: Install with DeepSeek Harness: dsh plugin add github:EternalNight996/memory-eternal / Install with DeepSeek Harness: dsh plugin add github:ysr666/dsh-vision-router
Scores use the published HOL methodology (v2026-10-27) — evidence quality, not a safety guarantee. “Not reported” means the registry has no value; it is not treated as no or zero.

Choose memory-eternal if…

  • you use Claude Code or Cursor or MCP. memory-eternal lists them; dsh-vision-router does not. [works_with]

Choose dsh-vision-router if…

No reported fact on this page sets dsh-vision-router alone apart. Compare the rows below against your needs.

memory-eternal vs dsh-vision-router, row by row

Comparison of memory-eternal and dsh-vision-router across every reported dimension
Dimensionmemory-eternal

eternalnight996/memory-eternal

dsh-vision-router

ysr666/dsh-vision-router

CategoryDeepSeek Harness PluginsDeepSeek Harness Plugins
Developer≠EternalNight996ysr666
DocumentationNot reportedNot reported
LicenseMITNot declared
Paid placementNoneNone
Plugin typePluginPlugin
Source repository≠https://github.com/EternalNight996/memory-eternalhttps://github.com/ysr666/dsh-vision-router
Apps00
MCP servers≠10
Skills≠21
Works with≠Claude Code, Cursor, DeepSeek Harness, MCPDeepSeek Harness
Directory listingsListed in 0 of 5 checkedListed in 0 of 5 checked
Owner verifiedYesYes
Release integrity0.49.25-alpha.1 recorded on 1 channel, no open notices3.4.0 recorded on 1 channel, no open notices
Security scanNeeds review (83/100, 17 findings)Needs review (83/100, 15 findings)
Trust score≠88/10089/100
GitHub stars≠2021286
Last updated≠2026-11-212026-11-19
Version≠0.49.25-alpha.13.4.0
Declared accessNot declaredNot declared
Install commandsInstall with DeepSeek Harness: dsh plugin add github:EternalNight996/memory-eternalInstall with DeepSeek Harness: dsh plugin add github:ysr666/dsh-vision-router
Sign-in requirementNot declaredNot declared

Every value comes from the public registry record shown for each side, measured on 2026-11-21. Rows marked ≠ differ between the two listings. Paid placement is disclosed and never changes any value here.

Install and compatibility

Install memory-eternal

  • Install with DeepSeek Harness

    $ dsh plugin add github:EternalNight996/memory-eternalSetup docs

Install dsh-vision-router

  • Install with DeepSeek Harness

    $ dsh plugin add github:ysr666/dsh-vision-routerSetup docs

Decision matrix

Which of memory-eternal or dsh-vision-router fits which priority
If your priority is…Better fitWhy
runtime fitmemory-eternalyou use Claude Code or Cursor or MCP. memory-eternal lists them; dsh-vision-router does not.[works_with]
Fields neither side disclosesNeither clearlyThe registry does not report documentation, license, declared access, sign-in requirement, so those needs cannot decide this comparison.[documentation, license, declared_access, sign_in]

Evidence and limitations

  • memory-eternal evidence: registry record · primary source, measured 2026-11-21
  • dsh-vision-router evidence: registry record · primary source, measured 2026-11-19
  • Not reported for at least one listing: documentation, license, declared access, sign-in requirement.
  • Registry scores summarize defined signals under the published HOL methodology; they are not a safety guarantee.
  • A missing field means the registry or the primary source did not report a value; it is not treated as no or zero.
  • Volatile fields can change after the verification time shown on each row.
  • Some security checks did not finish: Cisco skill scan and Cisco MCP scan.
  • 2 medium findings from the scan.
  • Some security checks did not finish: Cisco skill scan.
  • 2 medium findings from the scan.
  • No license declared in the manifest.

Questions about memory-eternal vs dsh-vision-router

Which should you pick for DeepSeek Harness?

Both memory-eternal and dsh-vision-router list DeepSeek Harness support, so the runtime alone does not decide. memory-eternal is the better fit when you use Claude Code or Cursor or MCP. memory-eternal lists them; dsh-vision-router does not. Both list DeepSeek Harness.

What is the main difference between memory-eternal and dsh-vision-router?

Developer differs: EternalNight996 versus ysr666. memory-eternal is the better fit when you use Claude Code or Cursor or MCP. memory-eternal lists them; dsh-vision-router does not. Both list DeepSeek Harness.

How current is this comparison?

It was verified against the registry on 2026-11-21. Each row carries its own measured time in the comparison record, and volatile fields can change after that timestamp.

What does the trust score mean here?

It is the published HOL trust methodology over defined registry signals. It compares evidence quality, not safety, and it never decides this page's recommendations. A scan is not a safety guarantee.