Tools & Capabilities

dsh-composition-check

aryswisnu/dsh-composition-check · ★ 0

aryswisnu

A local CLI that checks an ordered DSH profile bundle stack for simple Cordis patch ownership conflicts. It is an ordinary npm CLI package, not a DSH bundle.

License
MIT
Added
2026-08-23
Maintenance
active
Install kind
github

No manifest check is available; listing does not imply compatibility or security review.

安装

dsh plugin --profile web add github:aryswisnu/dsh-composition-check

GitHub 源码安装:首次需按提示配置 allowBuilds 构建授权后重试

For install and environment setup, plus plugin development tutorials, see DSH community docs ↗

README

Source README · body: en · Read Chinese README

Table of contents
  1. Install
  2. Stack file
  3. Use
  4. Findings and confidence
  5. Development

A local CLI that checks an ordered DSH profile bundle stack for simple Cordis patch ownership conflicts. It is an ordinary npm CLI package, not a DSH bundle.

Install

npm install --save-dev dsh-composition-check
# or: npm install -g dsh-composition-check

Stack file

profile: headless
bundles:
  - path: ./bundles/base
  - path: ./bundles/safe-delete

Each path is local and resolved relative to the stack file. A bundle must contain package.json declaring dsh.bundle.patch (accepted as dsh.bundle.patch or nested dsh.bundle.patch JSON fields) and the declared cordis.patch.yml inside that bundle directory.

Use

npx dsh-composition-check stack.yml
npx dsh-composition-check stack.yml --json
npx dsh-composition-check stack.yml --runtime

Default mode is static-only and never invokes DSH. --runtime creates a temporary DSH_HOME, runs dsh plugin --profile <profile> add <bundle> for each ordered layer, then dsh --profile <profile> --dump-config; the temporary home is removed in finally. It never deliberately modifies your existing DSH_HOME.

Exit status: 0 no errors, 1 checker/runtime errors, 2 usage or malformed input. In --json mode stdout is JSON only.

Findings and confidence

Static analysis reports duplicate inserted entry IDs as errors and later { id: ... } patches targeting earlier entries as override warnings. proven static means only that the listed local patch declarations were read and these rules found no errors. proven runtime means the requested DSH commands completed successfully in the temporary home. unknown means an error prevented that evidence. None of these states promises DSH compatibility: DSH preview provides no compatibility guarantee, and this tool does not model every Cordis or plugin interaction.

Malformed YAML/patch shapes and unreadable bundle contracts are reported as errors. The checker does not fetch packages, use network/model calls, validate arbitrary plugin code, or replace DSH integration testing.

Development

npm test
npm run typecheck
npm run build
npm run pack:check

See examples/stack.yml.