DSH Toolbox

dsh-plugin-catalog

A searchable catalog of DSH plugins, published as a plugin.

Version 2026.1113.20393 of dsh-plugin-catalog, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-plugin-catalog writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add dsh-plugin-catalog

Compatibility

dsh-plugin-catalog ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

A data package: no peers, no patch, no runtime row. It cannot conflict with anything you install, and it also cannot enforce that the versions it lists exist in your profile.

Who made it

Author: awesome-dsh-plugin. Repository: https://github.com/awesome-dsh-plugin/awesome-dsh-plugin. Package page: https://www.npmjs.com/package/dsh-plugin-catalog.

After install

It adds no interface. The package is a single JSON catalog; dsh plugin add dsh-plugin-catalog only writes the dependency row, and dsh --profile web --dump-config lists that row with nothing mounted behind it.

Files it touches

The catalog ships inside the package as plugins.json; the only file outside it is the dsh-plugin-catalog dependency line in $DSH_HOME/profiles/<name>/package.json.

Removing it

Removing dsh-plugin-catalog is the mirror command, dsh plugin --profile web remove dsh-plugin-catalog; nothing else references it, so nothing else breaks.

Common questions

What does it hook into, and how do I check that slot is free?

Its manifest names no community counterpart, so the check is manual: after dsh plugin add dsh-plugin-catalog, run dsh --profile web --dump-config and look for two rows claiming the same slot.

What happens when dsh upgrades?

Nothing declares a version window for dsh-plugin-catalog: dsh --version tells you what you are running, and no check will tell you whether dsh-plugin-catalog matches it.