This entry has been merged into: deepseek-harness-media — verification records were moved there; this page is kept as an archive.

deepseek-harness-provider avatar

deepseek-harness-provider

use glm/minimax/openai/claude api in your deepseek harness

PluginAI ModelsVisionNetworkVision / OCR
Verification
L1 · Found
Risk
Out of scope
Health
Active
Trust
Unrated

Install verification: No L4/L5 install test yetInstall verification details →

Data as of (UTC)

What it doesAI

Plugin to use GLM, MiniMax, OpenAI, and Claude APIs within DeepSeek harness.

  • Supports GLM, MiniMax, OpenAI, Claude APIs
  • Install as dynamic plugin or npm package
  • No modifications to harness source code
aiAI

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:lo2589/deepseek-harness-provider
tested artifact ccae3876d0c87d3ab2d5a88200afb8db72ca332f

Install method: GitHub · install spec not tested (L3 not tested)

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
package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
ccae38github2026-08-24

https://github.com/lo2589/deepseek-harness-provider

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

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/deepseek-harness-provider.svg)](https://www.dsh.so/artifact/deepseek-harness-provider/?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.

deepseek-harness-providerAutomated review · daily

Static high; dynamic no conclusion (static stands) → overall high.

static high→dynamic no conclusion→overall high
vet findings0 critical·2 high·17 medium
highoverall · high
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin version—
scanned versionb4ddfaec4cd2git2026-08-25
current versiondcffaadf965eversion moved on
vet verdictsuspicious · git

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

show static findings (5)
  • criticalchildProcess · code-execdsh-provider-quick-config/src/host.js:902

    let childProcess

  • criticalchildProcess · code-execdsh-provider-quick-config/src/host.js:903

    try { childProcess = require('node:child_process') } catch (e) { childProcess = undefined }

  • criticalchildProcess · code-execdsh-provider-quick-config/src/host.js:904

    if (childProcess === undefined) {

  • warningnetIp · networkdsh-provider-quick-config/src/client.js:194

    api: 'openai-completions', baseURL: 'http://127.0.0.1:8080/v1',

  • warningnetIp · networkdsh-provider-quick-config/src/client.js:274

    { key: 'mlx', displayName: '本地模型 (MLX)', baseURL: 'http://127.0.0.1:8080/v1' },

2model reads redacted source context · never executes plugin code

no dynamic conclusion (source harvest or model call failed) — no conclusion is not a pass; the overall rating falls back to the static tier.

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

• Repo created: 2026-08-14

• Stars: ★ 4 · Forks: 1

• Health: Active — committed within last 30 days

Source

GitHub: github.com/lo2589/deepseek-harness-provider

Frequently asked questions

What is deepseek-harness-provider?

deepseek-harness-provider 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 deepseek-harness-provider?

Run dsh plugin --profile web add github:lo2589/deepseek-harness-provider in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest, but its install spec is not verified yet (L3); sandbox install and runtime testing have not passed.

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-14 (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.

Was this page helpful?