What it may solve
会话级自动上下文压缩Plugin:回合中每步前 + 回合结束检测上下文用量,超过会话阈值自动 compact,摘要注入上下文后自然继续(DeepSeek Harness / DSH)
Imported third-party catalog description; not a Registry verification conclusion.会话级自动上下文压缩Plugin:回合中每步前 + 回合结束检测上下文用量,超过会话阈值自动 compact,摘要注入上下文后自然继续(DeepSeek Harness / DSH)
Author: JohnathonYe · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
会话级自动上下文压缩Plugin:回合中每步前 + 回合结束检测上下文用量,超过会话阈值自动 compact,摘要注入上下文后自然继续(DeepSeek Harness / DSH)
Imported third-party catalog description; not a Registry verification conclusion.— stars · 290 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 3 stars, 15 commits, 0 forks, and 0 watches; latest commit 2026-08-25.
Conclusion: Resolved npm release 1.3.0, published 2026-08-14, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 1 code capabilities: may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: auto-compact@1.3.0; SHA-256: a13067af1f7560f4ec4dd6d79e0852392f3c3c48d8e5df4dc18590eec815d4fc.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention auto-compact. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
auto-compactAnalyzed 1.3.0github:JohnathonYe/auto-compactExact version not resolved