Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
DSH Web UI plugin to drag/drop or paste local files/folders as attachments or reveal their real paths with a toggle.
- Drop or paste files/folders as attachments
- Toggle to show real paths instead of attachments
- Supports images, arbitrary files, and folders
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:djt889/dsh-drag-to-attachment#v1.0.3Install method: GitHub · runtime verified (L5)
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-15 · 9 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
10-06 → 11-15 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.0.3 | ✓ | ✓ | ✓ | ✓ | ✓ |
v1.0.3github✓ 17 runtime-verified2026-11-14
https://github.com/djt889/dsh-drag-to-attachment
✓dsh 0.2.2-rc.3current2026-11-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.5-rc.22026-09-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.3-alpha.22026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/djt889/dsh-drag-to-attachment#v1.0.3
ID: dsh-drag-to-attachment@v1.0.3@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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:
`[](https://www.dsh.so/artifact/dsh-drag-to-attachment/?ref=badge)``[](https://www.dsh.so/artifact/dsh-drag-to-attachment/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drag-to-attachment/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drag-to-attachment/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drag-to-attachment/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drag-to-attachment/?ref=badge-install)`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.
Static low; dynamic medium (authoritative when present) → overall medium.
v1.0.3dsh manifestv1.0.3git2026-11-17v1.0.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalshellExec · shell
lib/index.js:445async exec(command, args) { - warningchildProcess · code-exec
lib/index.js:59const child = spawn(EVERYTHING_EXE, ['-startup'], {
show 4 audit findings
- mediumGET /file serves any image file by absolute path with no allowlist or workspace confinement
lib/index.js:914Any caller able to reach the DSH web server (local process, LAN client, or a browser page via DNS-rebinding if the server does not validate Host) can read the full content of any .png/.jpg/.jpeg/.webp/.gif/.bmp file on the host up to 20MB, including screenshots, scans and photos outside every workspace. The handler performs no authentication and no root allowlist; only the extension and size are checked.
- mediumPOST /md5 returns the MD5 of any caller-supplied absolute file path
lib/index.js:239The route is an unauthenticated file oracle: it confirms existence and returns the content hash of ANY readable file (not only images), letting an attacker fingerprint host files, verify guessed contents, and (with chained requests) build a picture of the filesystem. The route is not even listed in the module's documented API header.
- mediumPlugin spawns a bundled, unverifiable prebuilt Everything.exe at host startup
lib/index.js:59On Windows, apply() unconditionally launches a native binary taken from the plugin's own vendor/everything directory with the host user's privileges, with no integrity check (no hash, no signature). That binary is neither part of the harvested source nor listed in package.json "files", so its behaviour cannot be audited here; if the distributed bundle carries it, arbitrary native code of the author's choosing runs on every boot. Conversely, if the binary is absent, spawn's asynchronous ENOENT 'error' event has no listener and can crash the host process.
- lowPOST /locate reads caller-supplied candidate paths and discloses host paths via unauthenticated full-disk search
lib/index.js:769The locator trusts request.candidates and reads/recursively lists/hashes those paths on the server, returning matched absolute paths and 'found' results; any caller can also trigger bounded-but-heavy walks over the home directory and all fixed drives (MAX_WALK_ENTRIES 1e5, 18s timeouts) and learn which absolute paths exist. Impact is limited to existence/disclosure and I/O load, since file contents are never returned by this route.
Host registers unauthenticated local routes that read any image by absolute path and MD5 any file, and spawns a bundled unverifiable Everything.exe; no remotely exploitable critical flaw found.
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-17 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is dsh-drag-to-attachment?
dsh-drag-to-attachment 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-drag-to-attachment?
Run dsh plugin --profile web add github:djt889/dsh-drag-to-attachment#v1.0.3 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-11-17 (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.
