Foreword

In DSH’s plugin usage, a single Profile can mount multiple capabilities, but the source, update, and rollback of third-party plugins still require explicit control. DSH STORE is a third-party plugin store and security lifecycle manager running within the DeepSeek Harness (DSH) settings page, maintained by AI-Scarlett. It does not develop an independent desktop application, does not modify DSH source code, and does not replace official @deepseek-ai/* packages.

What is this

DSH STORE’s package name/Bundle name is dsh-safe-plugin-manager. It completes plugin discovery, fixed-source installation, and lifecycle management within the DSH settings page, rather than splitting the installation action into an independent desktop app or manual scripts.

Verified capabilities include:

  • Reading plugins from the GitHub online directory; falling back to known snapshots released with the package when network access fails.
  • Physical isolation between the candidate discovery library and the trusted installation library; candidate entries must be promoted after passing review by a fixed Commit.
  • Support for searching by name, package name, category, or GitHub repository.
  • Support for 22 category filters, recommended pinning, and “Show Recommended Only” filtering.
  • Directory installation target fixed to a 40-digit Git Commit; does not accept npm-only, arbitrary download addresses, or floating branches.

Core Functions

Fixed-Source Installation

DSH STORE does not require users to trust a floating branch or arbitrary download address. The installation target in the directory is fixed to a 40-digit Git Commit, and the installation command points directly to that Commit. This ensures the installation entry point and source version are the same object, avoiding installation result drift after the branch continues to change.

Lifecycle Protection

Installations, updates, migrations, deactivations, activations, and uninstalls initiated from the store enter a one-time plan, precise confirmation, Profile pre-hash, backup, health check, and failure rollback process. The goal of this process is not “to get it installed,” but to make every package operation a confirmable and rollbackable action.

Guardian Restart Acceptance

DSH STORE provides an independent macOS launchd Guardian for heartbeat, Boot ID, restart, and runtime acceptance. After package operations are completed, the store marks “Pending Restart”; a one-time RESTART DSH <profile> plan is only generated when the Guardian heartbeat is normal.

Old Version Update Fix

Verified materials mention that the old version update security fix entry will use the official DSH CLI with --ignore-scripts, and --allow-build only when necessary. This is more conservative than opening up script permissions for the entire Profile and closer to the “fix only what’s necessary” approach.

Catalog Hierarchy and Compatibility

Catalog hierarchy compatibility includes: 2 MiB compatible bridge/main index, 512 KiB single detail limit, and failure shutdown. When directory read fails or integrity is inconsistent, it will not continue mixing untrusted data.

Pre-Installation Preparation

The first installation occurs when the manager is not yet running, so there is no plan confirmation, automatic backup, health check, or failure rollback protection. Before running the installation command, you must manually back up the following files for the target Profile (if they exist):

package.json
pnpm-lock.yaml
pnpm-workspace.yaml
cordis.patch.yml

The following uses the web Profile as an example. If the target Profile name is different, please replace web in the command.

Installation Command

Use fixed GitHub Commit to install:

dsh plugin --profile web add 'git+https://github.com/AI-Scarlett/DSH-Store.git#0bc733064bfc8ff16f6e8144188a7ac563092e12'

Do not change the Commit to floating branches like main, and do not bypass the DSH CLI to run pnpm or manually edit the Profile. When the command fails, keep the full error and pre-installation backup; do not execute repeatedly.

Enablement and Acceptance

After the above steps, it is recommended to verify in the following order:

  1. Run the following command to confirm the configuration can be successfully synthesized:
   dsh --profile web --dump-config
  1. In the store, install the DSH Guardian provided with the package using an independent plan. The Guardian is an independent macOS launchd Guardian used for heartbeat, Boot ID, restart, and runtime acceptance.
  2. After package operations are completed, wait for the store to mark “Pending Restart”. A one-time RESTART DSH <profile> plan is only generated when the Guardian heartbeat is normal.
  3. After enabling the Guardian, do not manually run pnpm dsh web or dsh web, otherwise a second instance may exit with EADDRINUSE.
  4. If there is an anomaly, submit the original error on GitHub Issues; do not submit credentials, complete Profile files, or environment variables.

Typical Usage

Search and Filter

You can search by name, package name, category, or GitHub repository in the store. Category filtering, recommended pinning, and “Show Recommended Only” are suitable for narrowing down the candidate scope first, then viewing the source and status of specific plugins.

Fixed Commit Installation

Use the 40-digit Git Commit fixed in the directory during installation. A verified example is:

dsh plugin --profile web add 'git+https://github.com/AI-Scarlett/DSH-Store.git#0bc733064bfc8ff16f6e8144188a7ac563092e12'

Package Operations and Rollback

Installations, updates, migrations, deactivations, activations, and uninstalls are all initiated from the store. Operations enter a one-time plan, precise confirmation, Profile pre-hash, backup, health check, and failure rollback process. The complete “install-restart-deactivate-activate-update-uninstall-rollback” loop for a real production Profile is still an independent acceptance item and cannot be replaced by test results.

Suitable Scenarios and Notes

Suitable for the following usage:

  • Need to manage third-party DSH plugins within a single settings page entry.
  • Want plugin source fixed to an explicit Commit rather than a floating branch.
  • Want installations, updates, deactivations, activations, and uninstalls to have confirmation, backup, health checks, and failure rollback.
  • Want Guardian to handle heartbeat, Boot ID, and runtime acceptance after restart.

Pay attention to:

  • DSH STORE is a third-party plugin store, not the official DSH app store.
  • Third-party plugins run with the available permissions of the current DSH process/Profile; check the source code, license, and actual runtime permissions before use.
  • Verified materials do not provide a license; the star count is also unconfirmed.
  • You must manually back up the target Profile files before the first installation because the manager’s protection has not yet taken effect.
  • Do not change the Commit to a floating branch, and do not bypass the DSH CLI to operate on the Profile directly.
  • Do not execute repeatedly when the command fails; keep the full error and pre-installation backup.

Links

  • GitHub Repository: https://github.com/AI-Scarlett/DSH-Store
  • Directory Page: Verified materials do not provide a fixed URL; the directory source relies on the GitHub repository and immutable Commit.