Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Connects DeepSeek Harness to Atlassian's official remote MCP server (Jira, Confluence, JSM, Bitbucket, Compass) over OAuth 2.1.
- OAuth 2.1 auth to Atlassian's official remote MCP server
- Single connection covers Jira, Confluence, JSM, Bitbucket, Compass
- Exposes Atlassian tools to DSH agents via MCP
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.
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); the npm pair from every snapshot.
8 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 11-01 · 8 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-02 → 11-01 · 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
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:zhenyong97/dsh-plugin-atlassian#v0.1.0Install method: GitHub · sandbox install failed (L4)
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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.0-rc.1 <0.1.5 || >=0.1.5-rc.1 <0.2.0-0 ×1
✗ Running dsh 0.2.1-rc.5 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-plugin-atlassian@0.1.0 0.2.1-rc.5 (the exemption lives in the local profile; this site does not assume one)
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).
| plugin ＼ dsh | dsh 0.2.1-rc.5 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
v0.1.0github10 failed2026-10-31
https://github.com/zhenyong97/dsh-plugin-atlassian
✗dsh 0.2.1-rc.5current2026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
This level was not executed in this scan.
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-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
This level was not executed in this scan.
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-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/zhenyong97/dsh-plugin-atlassian#v0.1.0
ID: dsh-plugin-atlassian@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
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-plugin-atlassian/?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.
Static low; dynamic medium (authoritative when present) → overall medium.
v0.1.0dsh manifestv0.1.0git2026-11-01v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
dev/cdp.mjs:152const response = await fetch(`http://127.0.0.1:${port}/json/list`) - warningnewFunction · code-exec
dev/verify-client-bundle.mjs:50new Function('window', 'document', source)(globalThis.window, globalThis.document) - warningnetIp · network
dev/verify-open-url.mjs:46const opened = await openInBrowser(`http://127.0.0.1:${port}/probe${QUERY}`) - warningnetIp · network
src/oauth.ts:42return `http://127.0.0.1:${this.#port}/callback` - warningnetIp · network
src/oauth.ts:157const parsed = new URL(url, 'http://127.0.0.1') - warningchildProcess · code-exec
src/open-url.ts:79const child = spawn(command, args, {
show 2 audit findings
- mediumHTTP routes register and serve with no request fence whenever the `connection` service is absent
src/routes.ts:132src/index.ts resolves the fence lazily (`scope.get('connection')`) and registers routes anyway when it is undefined, logging only a warning. Until the fence appears — or forever in a profile with a web server but no `connection` row — POST /transition, /connect and /disconnect and GET /board, /issue/<key>, /debug-tools are handled with no authentication. readJsonBody never checks Content-Type, so a cross-site `fetch(..., {mode:'no-cors', headers:{'content-type':'text/plain'}, body:'{"key":"ABC-1","transitionId":"31"}'})` (or a text/plain form) is parsed as JSON: any web page the user visits ca
- mediumReflected XSS on the loopback OAuth callback page via the error_description query parameter
src/oauth.ts:170`#respond` (src/oauth.ts:188-195) writes the message straight into `<p>${message}</p>` with `content-type: text/html`, so a crafted link such as http://127.0.0.1:3334/callback?error=x&error_description=<img src=x onerror=...> yields script execution on the predictable loopback origin while the plugin runs. Any visited page can load it in an iframe (no X-Frame-Options/CSP) — the blast radius is limited because that origin exposes only /callback, but it is attacker-controlled code in a loopback context, and the error branch fires before the state check, so the same cross-site GET also aborts a p
Two medium issues: the loopback OAuth callback page reflects error_description into HTML unescaped, and the plugin's HTTP routes can register without the host request fence.
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-09-18 · activity: Stable
• Repo created: 2026-09-18
• Stars: ★ 0 · Forks: 1
• Health: Stable — committed within 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-plugin-atlassian?
dsh-plugin-atlassian 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-atlassian?
Run dsh plugin --profile web add github:zhenyong97/dsh-plugin-atlassian#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, 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-01 (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.