@Lucky020/dsh-delivery-kit

交付工坊：从代码仓库与运行中的系统生成验收材料（数据库设计/概要设计/详细设计/使用说明书/测试报告/上线报告/验收报告/技术协议）。DeepSeek Harness 插件。

PluginDataOffice automationDatabase

Verification

L5 · Run tested

Verified

Risk

LowRisk

Health

Active

Trust

Gold

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked 10-30Install verification details →

Data as of 2026-10-30 (UTC)

What it does

Installation

dsh plugin --profile web add github:Lucky020/dsh-delivery-kit

verified

Install method: npm · runtime verified (L5) · verified on dsh 0.2.1-rc.3

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 matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.3
0.3.5	·

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

0.3.5npm2026-10-30

dsh-delivery-kit

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

Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).

Author badges

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

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-delivery-kitAutomated 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 versionv0.3.5dsh manifest

scanned version0.3.5npm2026-10-30

current version0.3.5same version

vet verdictclean · npm

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

show static findings (4)

warningchildProcess · code-execlib/delivery/runtime.js:29
const child = spawn(chrome, [
warningnetIp · networklib/delivery/tools.js:243
base_url: { type: 'string', description: '使用说明书用：系统当前访问地址，如 http://127.0.0.1:8080（系统在运行才会自动截图）' },
warningchildProcess · code-execlib/pyrun.js:12
const child = spawn(PYTHON, [script, ...args], {
warningchildProcess · code-execlib/screens.js:268
const child = spawn(chrome, args, { signal })

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-10-30 · activity: Active

• Repo created: 2026-10-30

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/Lucky020/dsh-delivery-kit

Frequently asked questions

What is @Lucky020/dsh-delivery-kit?

@Lucky020/dsh-delivery-kit 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 @Lucky020/dsh-delivery-kit?

Run dsh plugin --profile web add dsh-delivery-kit in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).

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-10-30 (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.