What it may solve
OpenTelemetry traces backend for the DeepSeek Harness telemetry seam: folds agent session events into OTLP span trees
Imported third-party catalog description; not a Registry verification conclusion.OpenTelemetry traces backend for the DeepSeek Harness telemetry seam: folds agent session events into OTLP span trees
Author: CodePrometheus · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
OpenTelemetry traces backend for the DeepSeek Harness telemetry seam: folds agent session events into OTLP span trees
Imported third-party catalog description; not a Registry verification conclusion.CodePrometheus/dsh-observability
— stars · 544 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: 2 stars, 8 commits, 0 forks, and 0 watches; latest commit 2026-08-15.
Conclusion: Resolved npm release 0.1.0, published 2026-08-15, 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: dsh-observability@0.1.0; SHA-256: 0afc5153c4e80b5c6cd3c4860fa5e98aa5701a009035a4f149b7b282ada25362.
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 dsh-observability. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-observabilityAnalyzed 0.1.0github:CodePrometheus/dsh-observabilityExact version not resolved