DSH Plugin Registry
中文EN
Submit plugin
Plugins/dsh-profile-settings

dsh-profile-settings

Automated evidence available

Per-profile settings overlay for DeepSeek Harness: global settings.yaml stays the baseline while each profile overrides any namespace through its own profiles/<name>/settings.patch.yml — object sections merge recursively, scalars and arrays replace wholesale, and !unset masks an inherited value. The overlay is transparent to existing plugins (they keep reading ctx.settings unchanged), writes land in the profile overlay only, and official schema validation, revision semantics, expectedRevision conflicts, watchers and events are untouched. Ships a settings command family (get/set/unset/mask/unmask/promote/demote/migrate/diff/layers) plus a Profile Settings section in the web Settings panel over a loopback RPC channel.

Author: XMoon · Tools & Capabilities · Catalog snapshot: 2026-09-19

Canonical semantic path

Plugin Management & RuntimeResource Configuration Workbench

One primary path; alternate capabilities remain separate.
cli.command-familyfile.yaml-patchinginterface.settings-panelruntime.hot-reload

What it may solve

Per-profile settings overlay for DeepSeek Harness: global settings.yaml stays the baseline while each profile overrides any namespace through its own profiles/<name>/settings.patch.yml — object sections merge recursively, scalars and arrays replace wholesale, and !unset masks an inherited value. The overlay is transparent to existing plugins (they keep reading ctx.settings unchanged), writes land in the profile overlay only, and official schema validation, revision semantics, expectedRevision conflicts, watchers and events are untouched. Ships a settings command family (get/set/unset/mask/unmask/promote/demote/migrate/diff/layers) plus a Profile Settings section in the web Settings panel over a loopback RPC channel.

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

XMoon/dsh-profile-settings

1 stars · 336 downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.

Analysis complete

Source structure

Conclusion: The source structure check completed without finding a structural issue.

Analysis complete

Repository health

Conclusion: The GitHub repository is reachable and not archived. Public data: 2 stars, 36 commits, 0 forks, and 0 watches; latest commit 2026-08-23.

Analysis complete

npm release

Conclusion: Resolved npm release 0.1.0, published 2026-08-23, license MIT.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis complete

Static risk scan

Conclusion: The scan observed 3 code capabilities: may read environment variables, may create or modify files, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.

Analysis complete

Package integrity

Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @xmoon76/dsh-profile-settings@0.1.0; SHA-256: 805e4576842bdfa457615cf0b0a34b52ba4d4cf58d6900548a998e75a19be168.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-profile-settings. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.

Install or update the plugin manager (latest)