JohnXu22786/session-export

Name: JohnXu22786/session-export
Author: JohnXu22786

Bundle捆绑包 Native原生 ⭐ 2 MIT Sessions & Context会话与上下文

Session export, redaction and compliance archiving bundle for DeepSeek Harness (dsh).

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-session-export is a DeepSeek Harness plugin for exporting and archiving sessions for compliance. It turns current or historical sessions into sanitized, verifiable archives in Markdown, JSONL, or PDF (via headless Chromium), organizes them on disk by session and date, and exposes list, search, delete, and trend/audit views. Deterministic redaction runs by default, masking API keys, JWTs, .env values, URL credentials, and absolute paths with salted SHA-256 fingerprints before anything reaches disk, so identical inputs map to identical placeholders without exposing secrets. Requires Node 24+. When no Chromium binary is found, PDF exports fall back to self-contained HTML and surface a warning. MIT licensed.

dsh-session-export 是 DeepSeek Harness 的会话导出与合规归档插件，将当前或历史会话转为可核验的脱敏归档。支持 Markdown、JSONL、PDF（基于无头 Chromium）格式，按会话/日期组织在磁盘上，并提供列表、搜索、删除与趋势审计视图。默认启用确定性脱敏：API 密钥、JWT、.env、URL 凭据与绝对路径在落盘前即被替换为带 SHA-256 指纹的占位符，相同输入产生相同输出，便于跨文件关联且不泄露密钥；可选盐值进一步强化指纹。需要 Node 24+，PDF 引擎缺失时会降级为 HTML 并发出警告。MIT 许可。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：session-export（JohnXu22786/session-export）
仓库：https://github.com/JohnXu22786/session-export
本站详情页：https://www.yhbd.top/plugins/johnxu22786-session-export/
本站登记：类型 bundle · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-08-20 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

Only 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile demo add github:JohnXu22786/session-export

把 JohnXu22786/session-export 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

10.1 KB · 缓存于 2026-09-02 19:39:08 · 10.1 KB

dsh-session-export

English | 简体中文

Session export & compliance archiving for DeepSeek Harness (dsh).

Turns any current or historical session into verifiable, sanitized archives in multiple formats, manages them on disk, and gives you a compliance/traffic view — all as a dependency-free dsh bundle.

Why

Exports are only useful for compliance or archival if they do not leak. This plugin combines, in one bundle:

Deterministic redaction by default — API keys, tokens, JWTs, .env-style lines, URL credentials and absolute file paths are masked before anything touches disk. The same input always yields the same output, and masked values carry a stable fingerprint so archives stay correlatable without leaking secrets.
Multiple formats — a readable Markdown narrative, a machine-readable JSONL full record, and PDF (print-ready HTML plus optional headless-Chromium rendering).
Archive management — exports are organized by session/date, discoverable, searchable, and deletable (with path-traversal guarding).
Compliance metadata — every export embeds a header with session id, models, sanitization level, counts, and an optional SHA-256 content hash; a trend/audit view summarizes what was exported, when, and how sensitive it was.
No model dependency — redaction is rule-based. An optional hook exists if you want to layer an LLM-assisted masker on top.

Features

1. Session export

Current or historical sessions, from the harness's own event log (ctx.sessionPersistence / ctx.sessions).
Formats: markdown, jsonl, pdf, or all.
Event-log folding is tolerant of unknown event types and payload shapes across harness versions.
Large exports are split into numbered parts (with a parts.json manifest); long messages can be truncated in Markdown with an explicit marker (JSONL always keeps the full record).

2. Redaction (on by default)

Rule	Description
`api-key`	`sk-…`, `pk-…`, `ghp_/gho_/github_pat_` (GitHub), `hf_`, `AKIA…`, `AIza…`, long base64-style tokens
`jwt`	`eyJ…` tokens
`high-entropy-token`	any 32+ char alphanumeric run
`env-value`	`KEY=value` assignment lines (e.g. pasted `.env`)
`bearer`	`Bearer`/`token` values
`url-credential`	`https://user:pass@host`
`absolute-path`	Windows drive / UNC / POSIX home paths — masked, or relativized to `<project-root>` when `pathMode: relative`
`email`	opt-in
`custom`	arbitrary user regexes

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 JohnXu22786/session-export 的 README.md。在 GitHub 查看原文 →