omdsh-dev/dsh-hub
OMDSH Hub reuses the Harness Profile, Bundle, Repository Plugin, Agent Preset, layered Skill registry and Cordis lifecycle contracts, then adds transactional installation, generation rollback, catalog browsing and a settings UI. Installed/Discover/collections/recipes/updates/history views are served by the prebuilt client entry, while the host side provides the extension manager, Workshop bridge and the official-v2 runtime-ready adapter. Its safety model stages install and update operations in a new physical Profile generation, disables package-manager lifecycle scripts by default, strictly parses registry documents with Ed25519 signature requirements for remote replacements, promotes a candidate generation only after configuration validation and runtime readiness confirmation, and keeps the previous generation recoverable when a candidate fails.
Install
⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.
Compatibility
Node.js 22 or later; the @deepseek-ai packages require registry read access. Integrates through the standard contracts: package.json#dsh.bundle, package.json#dsh.client, the settings.section client slot, the webServer host service, and loader readiness after every enabled Cordis fiber becomes active.
Details
- Repo: omdsh-dev/dsh-hub
- Category: Other
- Stars: 4
- Version: Release candidate checked against Cordis 4.0.1-rc.4 and the DSH client/host contracts 0.0.1-rc.5 (README queried 2026-08-13); package.json is private: true on purpose
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
The README notes the candidate was checked against the newest npm next-channel packages at the time (Cordis 4.0.1-rc.4, DSH client/host contracts 0.0.1-rc.5) and that the npm registry did not provide @deepseek-ai/dsh-repository-plugin, so Git-source catalog entries stay visible as guided integrations and OMDSH does not claim they can be installed through an npm-provided Repository Plugin.
FAQ
- How do I install OMDSH Hub?
- The README publishes no one-line install command, and the package is intentionally marked private: true so it is not on npm. Validation is local (npm ci --ignore-scripts, npm run validate, npm run pack:check); verify the current installation instructions in the repository first.
- What happens if an install or update fails?
- Install and update operations are staged in a new physical Profile generation. A candidate becomes current only after configuration validation and runtime readiness confirmation; failed candidates are discarded and the previous generation stays recoverable.
- Does OMDSH Hub require signing or registry access?
- Registry documents are strictly parsed and remote replacements require a configured Ed25519 signature. The @deepseek-ai packages need registry read access through a short-lived NPM_TOKEN; the README says never to commit a concrete token.