dsh-tg-bridge@1.20.2
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe setup finding resolves to a Telegram getMe diagnostic using the configured bot token, not command-output exfiltration. The manifest has no install lifecycle hook, and process startup and local persistence are part of the documented bridge setup.
Decision evidence
public snapshot- The manifest declares CLI scripts but no npm install lifecycle hook.
- The DSH plugin starts the bridge only when config.json exists, and supports disabling autostart.
- Setup uses the configured Telegram bot token for a getMe diagnostic request.
- Telegram API requests are directed to api.telegram.org.
- The package purpose is a Telegram bridge for DeepSeek Harness.
- The installer creates bridge autostart only when the user runs the installer; it also supports --no-autostart.
- Setup's process execution handles bridge restart and diagnostics; no unrelated command-output collector was identified.
Source & flagged code
9 flaggedSource executes local commands and sends command output to an external endpoint.
setup.mjs#virtual:normalized:round1View on unpkg · L107Findings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.20.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.20.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.