Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Lets DSH send and receive images in chat: local/web/AI-generated, plus vision reading via external API.
- Send local/web/base64 images as chat attachments
- Generate images via OpenAI-compatible API
- Read images with external vision API, disk-cached
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 imgpostInstall method: npm · 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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-03 · 7 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-02 → 11-03 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-19 → 11-14 · 76 points
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
08-19 → 11-16 · 77 points
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 |
|---|---|---|---|---|---|
| 0.3.1 | ✓ | ✓ | ✓ | ✓ | · |
| 0.1.1 | · | · | · | · | ○ |
| 0.1.0 | · | · | · | · | · |
0.3.1npm✓ 4 runtime-verified2026-11-16
imgpost
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · imgpost@0.3.1
ID: imgpost@0.3.1@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · imgpost@0.3.1
ID: imgpost@0.3.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
View checks & evidence
active in loader tree (200 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-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · imgpost@0.3.1
ID: imgpost@0.3.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-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.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · imgpost@0.3.1
ID: imgpost@0.3.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.
0.1.1npm2026-10-19
imgpost
○dsh 0.2.1-rc.22026-10-19not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
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-16not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
not present in web-profile loader inventory
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-11not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
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-09not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
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-29not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
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-25not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.7-rc.2 · profile: l3-fullscan
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
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-20not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-17not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
not present in web-profile loader inventory
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-13not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
not present in web-profile loader inventory
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-08not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
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-07not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
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-04not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04not tested
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · imgpost@0.1.1
ID: imgpost@0.1.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.0npm2026-09-08
imgpost
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:
`[](https://www.dsh.so/artifact/imgpost/?ref=badge)``[](https://www.dsh.so/artifact/imgpost/?ref=badge-install)``[](https://www.dsh.so/artifact/imgpost/?ref=badge-install)``[](https://www.dsh.so/artifact/imgpost/?ref=badge-install)``[](https://www.dsh.so/artifact/imgpost/?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.
v0.3.1dsh manifest0.3.1npm2026-11-170.3.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningnetIp · network
src/host.js:134if (port) return 'http://127.0.0.1:' + port; - warningnetIp · network
src/host.js:165if (port) return 'http://127.0.0.1:' + port; - warningbase64Decode · obfuscation
src/host.js:1231' $b=[Convert]::FromBase64String($env:IMG_B64)', - warningcurlDownload · network
src/host.js:1210' & curl.exe -sL -f --max-time 120 --proto "=https,http" --proto-redir "=https,http" --max-filesize 41943040 -o $p $env:IMG_URL',
show 3 audit findings
- mediumSettings endpoint can repoint the vision backend and keep the stored API key
src/host.jsThe guard's first layer is only 'remoteAddress is loopback'. In the plugin's own documented deployment (publicBaseUrl behind a reverse proxy that terminates TLS on this machine and forwards from 127.0.0.1) every remote request is a loopback peer, so the remaining barriers are a non-secret static header and an Origin check that is skipped when Origin is absent (plain curl). The source states host auth does not cover plugin-registered routes. An unauthenticated network client that can reach the GUI URL can POST a new primary/fallback baseURL; because a blank apiKey keeps the previous one, the st
- mediumImage URL download uses curl with redirects and no loopback/private-address filtering (SSRF)
src/host.jssend_image and imgpost_read_image accept any http(s) URL supplied by the model (hence prompt-injectable) and hand it to curl with -L, without the loopback/RFC1918/link-local/metadata blocking, DNS re-check, or per-hop redirect validation that downloadImageBytes applies to generation-result URLs. The plugin can therefore be made to issue GET requests to internal services (routers, local admin panels, cloud metadata endpoints) and follow attacker-controlled redirects; when the response is a real image it is stored as a chat attachment and/or uploaded to the external vision backend. curl also acc
- lowUnvalidated 'sha256:' attachment id enables path traversal in fallback attachment path
src/host.jsOnly the 'sha256:' prefix is checked; the remainder is lowercased and used unvalidated. readAttachmentBytes(null, ...) skips host verification, and attachmentHostPath falls back to path.join(<dshHome>/attachments/v1/objects, sha.slice(0,2), sha), which normalises '..' segments, so an argument like 'sha256:../../../../<path>' resolves outside the attachment store and is read with fs.readBytes. Impact is bounded: the bytes must pass magic-number, structure and a full host decode as a real image, and a local absolute image path is already an accepted argument of the same tool, so this is not a ca
Image validation and PowerShell handling are careful, but a weakly guarded settings endpoint can repoint the vision backend and leak the stored key, and URL downloads lack SSRF filtering.
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-22 · activity: Active
• Repo created: 2026-08-15
• Stars: ★ 2 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/hige6/imgpost
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 imgpost?
imgpost 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 imgpost?
Run dsh plugin --profile web add imgpost 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.
