The core philosophy of DSH is “everything is a plugin.” When introducing community plugins, version mismatches (such as Node version or peer dependencies) or missing manifests may cause service crashes or prevent startup. The dsh-install-guard plugin is used to intercept such risks before installation.

What Is This

This is a pre-installation compatibility preflight guard for DeepSeek Harness. It is maintained by user 618527 and, through static checks and runtime validation, ensures that a plugin to be installed is compatible with the current DSH environment.

Core Features

The plugin provides the following inspection and validation capabilities:

  1. engines.node check: Compares the engines.node requirement declared by the plugin in package.json with the current Node environment version.
  2. @deepseek-ai/* peers check: Compares peer/dependency ranges with resolved versions to prevent core package version conflicts.
  3. dsh manifest check: Checks whether the plugin manifest declares required fields such as dsh.bundle.patch or dsh.client.
  4. Isolated trial start: Using the trial=true parameter, installs the plugin into a temporary configuration and runs apply to catch runtime or loading crashes.

Installation and Activation

Use the following command to add the plugin to the web configuration file:

dsh plugin --profile web add dsh-install-guard

After installation is complete, restart dsh web to activate the plugin.

Typical Usage

The plugin registers a tool named plugin_install_guard, which can be invoked through conversational commands. It is usually divided into two steps:

  1. Check compatibility:
    plugin_install_guard { spec: "plugin-name", action: "check" }

To run an isolated trial start, add `trial: true` to the parameters.
  1. Confirm and then install:
    plugin_install_guard { spec: "plugin-name", action: "install", resolution: { spec: "plugin-name@compatible" } }

Applicable Scenarios and Notes

  • Applicable scenarios: DSH plugin developers and administrators who need strict control over environment compatibility.
  • Trigger method: This tool is actively triggered; it is not an automatic hook for the marketplace install button.
  • Risk note: Static checks and isolated trial starts can reduce, but cannot eliminate, all third-party code risks. The source code and license should be reviewed before installation.
  • Ecosystem integration: It can be used together with dsh-doctor (environment health) and dsh-poison-guard (security/audit) to build a complete pre-installation check pipeline.

Summary

dsh-install-guard provides comprehensive preflight capabilities, from dependency versions to runtime behavior, making it a practical tool for reducing the risk of introducing DSH plugins and improving system stability.