Before copying a command

  • Confirm the listing says Plugin Bundle—not Skill, App, Integration, or Resource.
  • Check the target Profile and Harness compatibility baseline.
  • Open the immutable manifest and patch evidence.
  • Review lifecycle scripts and the listed network, filesystem, credential, shell, or external-runtime facts.

Install one pinned Bundle

Use the exact version-pinned command on the artifact page. This example shows the command shape; use the package and Profile for the Bundle you selected.

dsh plugin --profile web add package-name@1.2.3

Verify before real work

List the Profile’s plugins, restart the Profile if the maintainer requires it, and exercise the smallest non-sensitive scenario.

dsh plugin --profile web list

Update or remove deliberately

  • Read release and manifest changes before updating.
  • Use the artifact page’s update command only after confirming the intended version.
  • Keep the removal command and any separate data-cleanup note available.
  • If verification fails, remove the new Bundle and return to the known-good Profile before testing another change.

Why DSHub says Evidence-verified

DSHub checks the Bundle structure, immutable source commit, package distribution, and review record. It does not execute third-party code or promise that a Bundle is safe or compatible with every machine.

Choose an evidence-verified Bundle →