@dragonsummer1/dsh-watermark-remover

DSH 插件：结构级无损移除 PDF / Word 水印（探测 Form XObject 图层与文字块，不改动正文与分辨率）

PluginProductivityOffice automationVision / OCR

Verification

L3 · Install spec

Risk

LowRisk

Health

Active

Trust

Silver

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

What it does

DSH 插件：结构级无损移除 PDF / Word 水印（探测 Form XObject 图层与文字块，不改动正文与分辨率）

Installation

dsh plugin --profile web add github:dragonsummer1/dsh-watermark-remover

verified

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

v0.1.0github2026-10-28

https://github.com/dragonsummer1/dsh-watermark-remover

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 official badges in your README to showcase security & install-test status:

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-watermark-removerAutomated 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.1.0dsh manifest

scanned versionv0.1.0git2026-10-28

current versionv0.1.0same version

vet verdictclean · git

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

show static findings (4)

warningfsWrite · fileslib/docx-watermark.js:242
fs.writeFileSync(outPath, outBuf);
warningfsWrite · fileslib/pdf-watermark.js:538
fs.writeFileSync(outPath, outBytes);
warningfsWrite · filessrc/docx-watermark.ts:222
fs.writeFileSync(outPath, outBuf)
warningfsWrite · filessrc/pdf-watermark.ts:518
fs.writeFileSync(outPath, outBytes)

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

• Repo created: 2026-10-27

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/dragonsummer1/dsh-watermark-remover

Plugin notes

What is the @dragonsummer1/dsh-watermark-remover DeepSeek Harness plugin?

@dragonsummer1/dsh-watermark-remover is a DeepSeek Harness plugin maintained by @dragonsummer1. It is cataloged on dsh.so as a Productivity plugin for Office automation tasks, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install @dragonsummer1/dsh-watermark-remover?

Run dsh plugin --profile web add github:dragonsummer1/dsh-watermark-remover#v0.1.0 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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static scan verdict (vet primary, dsh backstop) applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-27