DeepSeek Harness Plugin

Run API relay audits from DeepSeek Harness

The v2.5.0 candidate DSH bundle registers /relay-audit on compatible web and cc-tui profiles and reuses the selected route. This adapter currently requires the selected model route to declare Claude.

API Relay Audit does not certify that a relay is safe. Results remain local evidence with explicit clean, anomaly, and inconclusive states.

Install the immutable release

Official rc.6 Web and dsh-cc-tui 0.4.1 composition passed in CI. Isolated Web installs, boot, and installed-handler connectivity passed on DSH 0.1.7-rc.2 and 0.2.0-rc.2. Interactive command rendering and Desktop profiles remain unverified; start with an isolated profile.

DSH_PLUGIN_REF=v2.5.0
dsh plugin --profile web add "github:toby-bridges/api-relay-audit#${DSH_PLUGIN_REF}"
dsh plugin --profile cc-tui add "github:toby-bridges/api-relay-audit#${DSH_PLUGIN_REF}"

Run the audit

Start with --connectivity. The full audit sends more requests and may incur metered relay charges.

# Lower-cost route and credential check
/relay-audit --connectivity

# Full 14-step audit
/relay-audit

# Profile-gated Web3 relay audit
/relay-audit --profile web3 --fast-context

Runtime boundaries

The plugin requires the DSH profile loader and @deepseek-ai/dsh-commands registry.
The selected route must identify as Claude; current identity and stream baselines are Claude-specific.
The DSH adapter resolves the credential on every invocation and passes it to the audit process through API_RELAY_AUDIT_KEY, not that process's argv.
v2.4.1 passes error-probe and streaming curl credential headers through curl config stdin. The older v2.4.0 release can put the key in curl process arguments while those requests run.
Reports are written under the current session workspace by default.

Evidence scope

The plugin preserves separate API relay audit, prompt injection audit, model substitution signals, and Web3 relay audit query families. Model identity is a consistency signal, not standalone provider proof. The v2.4.1 host checks covered connectivity mode against a local fixture; they do not cover a full audit or an interactive Web session.

Review the candidate scope in the v2.5 release notes. A draft alone does not make pinned downloads available. The v2.4.0 distribution verification remains historical evidence for that tag.