runseal-labs/dsh-tool-runseal

Replaces dsh's built-in sandbox with RunSeal: an OS-native, policy-governed execution environment with filesystem, process, resource and network boundaries plus audit events.

Every execution emits audit events (execution.requested, policy.resolved, execution.finished) and streaming stdout/stderr is forwarded with the exit code. Setup or backend failures fail closed — the command is rejected with a runseal: error and a non-zero exit rather than silently passing through to the unsandboxed path. Environment credentials are scrubbed before execution, so a confined command does not inherit the operator's secrets.

Infrastructure & Deployment ★ 0
View on GitHub ↗

Install

dsh plugin --profile web add dsh-tool-runseal@0.2.4

The versioned npm line; the package resolves on the public registry and its registry metadata points back at this repository. Plugin 0.2.4 pins RunSeal 0.2.2, and the README states the plugin is fully out-of-tree — it depends only on published dsh base packages and needs no dsh source changes.

Compatibility

Adapted against unmodified dsh master (published packages 0.2.1-rc.2). It registers both ctx.sandbox and ctx.subprocess: confine() wraps argv through a thin Node wrapper that runs the command under runseal rpc, and ordinary subprocess calls run through RunSeal with explicit danger-full-access. dsh's read-only and workspace-write levels map onto RunSeal sandbox levels, keeping the caller's cwd separate from writable workspace roots; network modes are unmanaged (default), disabled, or proxy with credential redaction for enterprise routing.

Details

Alternatives

ShehabYahya/DSH-Tool-Gate · beex-labs/dsh-desktop-plugin · leoswing/dsh-tool-grafana

More plugins in Infrastructure & Deployment

Browse more in Infrastructure & Deployment

Guides for Infrastructure & Deployment plugins