Bundle
dsh-guardian
Dangerous-operation policy, canonical output redaction, and security review for DeepSeek Harness.
- Source
- lonelymoon87
- stars
- 2 stars
- License
- MIT
- Updated
- Updated 16 hours ago
Readme
# dsh-guardian
[](https://github.com/lonelymoon87/dsh-guardian/actions/workflows/ci.yml)
[](https://github.com/lonelymoon87/dsh-guardian/actions/workflows/dsh-compatibility.yml)
[](https://github.com/lonelymoon87/dsh-guardian/releases/latest)
[](./LICENSE)
Runtime dangerous-operation policy, canonical output redaction, and security-review workflow for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness).
The v0.1.3 release is tested with DSH 0.1.0-rc.8 and 0.1.1-rc.1 while retaining the rc.6-compatible peer range. Prebuilt packages are distributed through GitHub Releases. The unscoped npm name is owned by another publisher, so this project is not published there.
[简体中文](./README.zh-CN.md)
## MVP
- A `tools/pre-execute` waterfall classifies dangerous shell, SQL, and structured file-write arguments as `deny`, `ask`, or unchanged.
- `standard`, `strict`, and `permissive` profiles provide different approval levels while retaining non-negotiable deny rules.
- Custom regular-expression rules add deployment-specific `deny` or `ask` decisions.
- A `tools/post-execute` waterfall redacts common credentials from canonical JSON results, failures, rendered text, and block feedback.
- Consecutive text blocks are scanned as one stream so splitting a credential across blocks does not bypass redaction.
- `/security-review` loads a bundled, read-only security-review skill.
The MVP is not a process sandbox, authorization system, data-loss-prevention service, or substitute for the provider policies mounted below it.
## Policy behavior
The built-in rules deny recursive forced deletion of root or home paths, network-response pipes into shells, raw writes to `/dev`, and writes to `/etc`. Force pushes, destructive SQL, and other recursive forced deletions ask for approval. Strict mode additionally asks for `sudo`; permissive mode retains only deny rules.
Guardian always delegates through `next()`. When another policy listener returns a decision, the most restrictive result wins: `deny` outranks `ask`, which outranks `allow`.
## Redaction behavior
Built-in patterns cover AWS access-key IDs, GitHub tokens, `sk-` API keys, PEM private-key blocks, and common credential assignments. Redaction is applied to the canonical JSON value when one exists, preserving arrays, objects, numbers, booleans, and null values. This prevents Code Mode and downstream renderers from retaining an unredacted value behind safe-looking display text.
Logs contain only the tool name, match count, and redaction labels. The plugin does not append custom session events because the current external plugin API does not expose an ignorable event envelope; emitting a required unknown event would make old sessions unreadable after uninstall.
## Permissions and data
- Guardian inspects tool names, arguments, canonical results, and rendered output inside the current DSH process. It can deny a call or request approval but never executes the requested operation itself.
- Redaction replaces matched secret text before downstream model-visible consumers receive the canonical result. Logs retain only the tool name, match count, and non-secret labels.
- The plugin does not read credential stores, make network requests, write workspace files, transmit telemetry, or persist custom session events.
## Install
The package supports DSH `>=0.1.0-rc.6 <0.2.0` plugin APIs and Node.js `^22.19 || >=24`.
```sh
dsh plugin --profile web add https://github.com/lonelymoon87/dsh-guardian/releases/download/v0.1.3/dsh-guardian-0.1.3.tgz
```
The release tarball is prebuilt and needs no build allowance. A pinned source install is also supported:
```sh
dsh plugin --profile web add github:lonelymoon87/dsh-guardian#v0.1.3
```
The source install runs this package's `prepare` build. pnpm 10 and later reject it until the profile allowlists the exact package key printed by the failed command; apply that instruction and rerun the same `dsh plugin add` command. Replace `web` with `headless` to install into the one-shot agent profile.
To upgrade, rerun `dsh plugin add` with the newer release URL. To uninstall:
```sh
dsh plugin --profile web remove dsh-guardian
```
## Configuration
```yaml
- id: guardian
name: dsh-guardian
config:
profile: standard
rules:
- name: production-host
pattern: production\\.internal
action: ask
reason: production target requires review
redaction:
enabled: true
patterns:
- label: internal-token
pattern: INT_[A-Z0-9]{12}
```
Regular-expression flags may contain only `i`, `m`, `s`, and `u`. Invalid expressions and labels fail during plugin loading.
## Verification
The tests cover positive and negative cases for every built-in rule, structured paths, profile behavior, downstream policy composition, nested canonical values, custom credentials, block feedback, split text blocks, disabled redaction, command dispatch, and invalid configuration.
- The v0.1.3 tarball installs directly from its HTTPS release URL into clean DSH 0.1.0-rc.8 and 0.1.1-rc.1 profiles.
- The packed bundle and pinned GitHub source install both appear in `dsh --dump-config`.
- CI covers Node 22.19 and Node 24; a compatibility matrix repeats the real install against DSH 0.1.0-rc.8 plus the `latest` and `next` npm tags.
- Bugs and compatibility reports are tracked in [GitHub Issues](https://github.com/lonelymoon87/dsh-guardian/issues).
## License
[MIT](./LICENSE)
Install
dsh plugin --profile web add github:lonelymoon87/dsh-guardian
Profile: web
With the hub plugin installed, ask your agent to install it by name — it resolves the same plan shown here.
dsh plugin --profile web add github:stvlynn/dsh.fish#path:packages/dsh-plugin-hub
install dsh-guardian from the hub
- This package builds from source on install. pnpm will ask you to allow its build script — that is permission to run the package’s code on your machine, outside the agent sandbox. Only allow sources you trust.
- This source has no pinned commit, so a later push upstream changes what installs. Prefer pinning a commit.