dsh-tg-bridge@1.5.2
устаревшая сборка — ставьте 1.11.0 или новее
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected network and credential flows match the Telegram bridge and local harness functions. Agent-related changes are reached through explicit chat commands; the scanner hints did not establish a concrete attack.
Decision evidence
public snapshot- The manifest defines start and setup commands but no install lifecycle hook.
- The bridge sends Telegram bot API requests to api.telegram.org; its setup probe calls Telegram getMe.
- Provider keys are passed to the spawned DeepSeek Harness process as environment variables for a turn.
- Control commands change plugins or the DSH persona only when invoked through chat commands.
- The inspected runtime-operation locations handle transcription output, CLI diagnostics, process control, language state and log output.
- The restart helpers wait for an idle bridge or a delivered reply before restarting it.
Source & flagged code
6 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
setup.mjsView on unpkg · L19Findings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.5.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.5.2 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.