ssdyg4444-sys/dsh-audit-log

ssdyg4444-sys★ 0TypeScript最后同步: 2026-08-19

在 GitHub 打开

Runtime data-flow audit log for DeepSeek Harness: who mutated what, in what order - per-plugin, per-fiber attribution.

README 摘要

dsh-audit-log Who mutated my data flow? — Runtime data-flow audit log for DeepSeek Harness plugins, with per-plugin, per-fiber attribution. English 简体中文 dsh-audit-log answers the question every plugin ecosystem eventually asks: when a field in your session data disappears or gets rewritten, which plugin did it, in what order, and what exactly changed ? It is a read-only observer: it never blocks, never rewrites, and never stores payload values — only structural fingerprints (types, keys, lengths). Secrets never enter the log. Why Cordis (the framework under DeepSeek Harness) shares the same args array across every listener of a waterfall dispatch, and the internal/get / internal/set interception points are public. Any plugin can silently rewrite data flowing through the system. With hundreds of plugins, "which plugin washed out my field" is otherwise nearly impossible to answer. dsh-audit-log makes it answerable: - Dispatch-level diff — every audited dispatch snapshots argument shapes before and after, and records the mutations in between. - Per-listener window attribution — each listener is wrapped at registration; mutations are attributed to the exact plugin + fiber that performe…

在 GitHub 查看完整 README →
工具/开发auditdeepseek-harnessdshdsh-pluginobservability

分类