The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

dsh-plugin-lingxi avatar

dsh-plugin-lingxi

dsh-plugin: 把 DeepSeek Harness 会话记录与工作区产物导入为灵犀(金山办公)可接手的新任务

PluginAI ModelsAutomationMemoryFileStorage
Verification
L3 · Install spec
Risk
Out of scope
Health
Inactive
Trust
Silver

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

Data as of (UTC)

What it doesAI

Imports DeepSeek Harness session logs and workspace artifacts into Lingxi (WPS Office) as new tasks.

  • Parses session JSONL into readable Markdown conversation records
  • Preserves original conversation.jsonl for full traceability
  • Collects workspace artifacts into a self-contained import package
aiAImemoryAIfileAIstorageAI

Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.

Installation

dsh plugin --profile web add github:songying2024/dsh-plugin-lingxi
tested artifact 58b64661e240bade3bb22fd713af04ba9a9f5a6b

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
only the declared range >=0.0.0

Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages.

raw ranges>=0.0.0 ×1

✓ Running dsh 0.2.2-rc.5 is within the declared range — install is not blocked by version.

Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
58b646github2026-08-24

https://github.com/songying2024/dsh-plugin-lingxi

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-plugin-lingxi.svg)](https://www.dsh.so/artifact/dsh-plugin-lingxi/?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-plugin-lingxiAutomated 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)
plugin versionv0.1.0
scanned version0.1.0git2026-08-24
current version0.1.0same version
vet verdictclean · git

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

show static findings (2)
  • warningfsWrite · fileslib/importer.js:120

    fs.writeFileSync(convPath, header + markdown, 'utf8')

  • warningfsWrite · fileslib/importer.js:159

    fs.writeFileSync(manifestPath, JSON.stringify(manifest, null, 2), 'utf8')

2model 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-08-21 · activity: Inactive

• Repo created: 2026-08-21

• Stars: ★ 1 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/songying2024/dsh-plugin-lingxi

Frequently asked questions

What is dsh-plugin-lingxi?

dsh-plugin-lingxi 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 dsh-plugin-lingxi?

Run dsh plugin --profile web add github:songying2024/dsh-plugin-lingxi 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-08-24 (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?