What it may solve
Codex-style temporary side conversations for DeepSeek Harness.
Imported third-party catalog description; not a Registry verification conclusion.Codex-style temporary side conversations for DeepSeek Harness.
Author: Lukeknow0 · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Codex-style temporary side conversations for DeepSeek Harness.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 373 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: 4 stars, 48 commits, 0 forks, and 0 watches; latest commit 2026-08-23.
Conclusion: Resolved npm release 0.4.0, published 2026-08-23, 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 found 2 characteristics that need attention: may execute dynamically constructed code, may access the network. This is a bounded automated observation, not a determination of malicious intent.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @lukeknow0/dsh-side-chat@0.4.0; SHA-256: 7fdc3f9d9f3ed472fc2e9689c13cd79299daf2687a77f4f14f6d036cf65fa66f.
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 @lukeknow0/dsh-side-chat. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@lukeknow0/dsh-side-chatAnalyzed 0.4.0github:Lukeknow0/dsh-side-chatExact version not resolved