Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
Conversational A-share research assistant for stock screening, risk screening, market monitoring, and review via Tonghuashun financial API with local caching.
- Scenario routing for stock selection, screening, monitoring, review
- 28 endpoints for quotes, K-lines, financials, limit-up pools, dragon-tiger lists
- Company check fuses financials, valuation, anomalies, news; timestamped conclusions
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:ikomom/dsh-a-share-assistant#v0.2.0Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| v0.2.0 | ○ | ○ | ○ | · | · |
v0.2.0github○ 3 ecosystem plugin2026-10-19
https://github.com/ikomom/dsh-a-share-assistant
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/ikomom/dsh-a-share-assistant#v0.2.0
ID: dsh-a-share-assistant@v0.2.0@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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/ikomom/dsh-a-share-assistant#v0.2.0
ID: dsh-a-share-assistant@v0.2.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-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.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/ikomom/dsh-a-share-assistant#v0.2.0
ID: dsh-a-share-assistant@v0.2.0@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.
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:
`[](https://www.dsh.so/artifact/dsh-a-share-assistant/)`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 — stricter wins → overall medium.
v0.2.0v0.2.0git2026-10-21v0.2.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningfsWrite · files
src/cache.js:68fs.writeFileSync(tmp, JSON.stringify(index, null, 2)); - warningfsWrite · files
src/cache.js:75fs.writeFileSync(tmp, JSON.stringify(data, null, 2)); - warningchildProcess · code-exec
src/iwencai.js:194child = spawn(pythonBin(), args, { stdio, env }); - warningmanifest-fs-unfenced · sandbox
presets/a-share-assistant/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
presets/a-share-assistant/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
presets/a-share-assistant/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 5 audit findings
- mediumUnsanitized date/type in cache paths allow .json read/write outside the cache root
src/cache.js:114scripts/fetch-raw.mjs passes attacker/model-supplied --date and --save straight into saveSnapshot, so date like '../..' with type 'config' overwrites .a-share-assistant/config.json (or any reachable <name>.json such as package.json) with fetched API data; getByDate (line 192) and latest (line 167) apply the same unsanitized join on read, so the same traversal can disclose JSON files - including the config that holds the fuyao/iwencai API keys - if cli.js (not harvested) exposes them.
- mediumPreset hook silently strips all skill-catalog messages, hiding host skills from the model
presets/a-share-assistant/skill-quarantine.mjs:35Every session using this preset loses the <available_skills> catalog injected by DSH, so host-platform skills (including any security/guardrail tooling delivered as skills) become invisible and uncallable, while this preset's own skill stays loadable through an absolute SKILL.md path handed to the model. The install output never mentions this context change, so users cannot see the asymmetric capability removal.
- lowThird-party Python skill scripts inherit the full parent environment including API keys
src/iwencai.js:183Every iwencai search spawns a python script from ~/.agents/skills with the whole DSH process environment, so those vendor scripts receive FUYAO_API_KEY and any other secret in the environment, not just IWENCAI_API_KEY. install-iwencai-skills.mjs's own comments note the vendor CLI pulls skill packages over plain http://ms.10jqka.com.cn, widening the supply-chain blast radius.
- lowChannel slug is joined into the skills path and its first .py is executed
src/iwencai.js:45resolveChannel accepts any value whose <slug>/scripts directory exists and runs the first *.py found there via python; a slug such as '../../tmp/x' escapes SKILLS_ROOT. The same unvalidated key is embedded in the temp output path (`iwencai-${ch.key}-...json`) created with recursive mkdir, allowing redirected writes outside CACHE_ROOT. Exploitation requires a matching directory containing a .py to already exist, so precondition is real.
- lowMain runtime modules referenced by the package are absent from the provided source
package.json:18src/index.js, src/cli.js (imported by src/entry.js) and src/fuyao.js (imported by src/market.js) are not among the 14 harvested files, so the primary data-fetch client, CLI argument handling and API-key usage cannot be verified, and the plugin entry may fail to load as shipped.
No critical/high issues: cache paths allow .json read/write outside the cache root, and the preset silently strips the host skill catalog from the model context.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-12 · activity: Active
• Repo created: 2026-09-02
• Stars: ★ 0 · Forks: 1
• Health: Active — committed within last 30 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).
