@Qingzhu093/dsh-latex-studio

LaTeX compile gate + VTO typesetting loop for DeepSeek Harness: MiKTeX-native, 10 tools, 3 skills, persistent defect ledger, and a Plugins-page configuration form

Plugin

Verification

L5 · Run tested

Verified

Risk

Critical

Health

Active

Trust

Silver

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked 10-18Install verification details →

$Install verification badge dsh 0.2.1-rc.2$

What it does

LaTeX compile gate + VTO typesetting loop for DeepSeek Harness: MiKTeX-native, 10 tools, 3 skills, persistent defect ledger, and a Plugins-page configuration form

Installation

dsh plugin --profile web add github:Qingzhu093/dsh-latex-studio

verified

Install method: GitHub · runtime verified (L5)

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

author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current
baseline-0.1.0	·
429de4	✓

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

baseline-0.1.0github2026-10-21

https://github.com/Qingzhu093/dsh-latex-studio

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

429de4github✓ 1 runtime-verified2026-10-18

https://github.com/Qingzhu093/dsh-latex-studio

✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/Qingzhu093/dsh-latex-studio (version unstated)

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Passed

Install + runtime smoke verified in the dsh sandbox — installs and runs

L5 · runtime verified · valid for dsh 0.2.1-rc.2

ID: dsh-latex-studio@429de4@dsh0.2.1-rc.2 · profile: l3-fullscan

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-latex-studio@baseline-0.1.0@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

↳ carried from earlier record dsh-latex-studio@baseline-0.1.0@dsh0.2.1-rc.2 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

↳ carried from earlier record dsh-latex-studio@baseline-0.1.0@dsh0.2.1-rc.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:Qingzhu093/dsh-latex-studio · channel GitHub source · outcome ran · exit 0

check took: 1.8s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:Qingzhu093/dsh-latex-studio · channel GitHub source · outcome ran · exit 0

check took: 1.8s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:Qingzhu093/dsh-latex-studio · channel GitHub source · outcome ran · exit 0

check took: 1.8s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:Qingzhu093/dsh-latex-studio · install mode reused L4 scratch

check took: 18ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-18

ready line dsh web: http://127.0.0.1:62129/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-18

path / · HTTP 200 · took 18ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-18

verdict active · entries 150

match: include:latex-studio · dsh-latex-studio · phase active

phases: active 122 · null 28

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

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-latex-studioAutomated review · daily

Static low, dynamic high — stricter wins → overall high.

static low→dynamic high→overall high

0 critical·0 high

highoverall · high

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.1.0dsh manifest

scanned versionbaseline-0.1.0git2026-10-21

current versionbaseline-0.1.0same version

vet verdictclean · git

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

show static findings (5)

warningchildProcess · code-execlib/core/env.js:67
const res = spawnSync('reg', ['query', key, '/v', 'InstallLocation'], {
warningchildProcess · code-execlib/core/env.js:165
const res = spawnSync(executable, args, {
warningfsWrite · fileslib/core/report.js:324
fs.writeFileSync(jsonPath, JSON.stringify(payload, null, 2) + '\n', 'utf8')
warningfsWrite · fileslib/core/report.js:325
fs.writeFileSync(mdPath, rendered.markdown.endsWith('\n') ? rendered.markdown : rendered.markdown + '\n', 'utf8')
warningspawnShell · shelltools/install.mjs:78
const result = spawnSync(command, args, { stdio: 'inherit', ...options, ...(needsShell ? { shell: true } : {}) })

2dynamic auditmodel reads redacted source context · never executes plugin code

highest gradehigh

merged intooverall high

audited at2026-10-19

findings0 critical·1 high

show 1 audit findings

highWorkspace path guard bypass via Windows trailing-space `..` componentslib/core/paths.js:63
On Windows, Win32 strips trailing spaces from path components, so a model-supplied path such as `sub/.. /.. /secret` passes this exact `..` check; after `path.resolve` the OS treats each `.. ` as `..` and escapes the workspace. The module header states this is the only path validator used by daily/vto, and `resolveInside` has the same normalization gap, so file reads/writes intended to stay under the workspace can reach outside it.

Runtime helpers are mostly defensive, but the shared workspace path guard can be bypassed on Windows with trailing-space `..` components, letting model-supplied paths escape the workspace.

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

• Repo created: 2026-10-17

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/Qingzhu093/dsh-latex-studio

Plugin notes

What is the @Qingzhu093/dsh-latex-studio DeepSeek Harness plugin?

@Qingzhu093/dsh-latex-studio is a DeepSeek Harness plugin maintained by @Qingzhu093. It is cataloged on dsh.so as a Developer plugin, 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 @Qingzhu093/dsh-latex-studio?

Run dsh plugin --profile web add github:Qingzhu093/dsh-latex-studio#baseline-0.1.0 in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl 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 (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, and its conclusion can only raise the combined verdict, never exempt it. 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-17

@Qingzhu093/dsh-latex-studio

What it does

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README