dsh-tg-bridge@1.21.0
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 flagged setup behavior reads a configured Telegram bot token and verifies it with Telegram’s own API, while the process and autostart behavior serves the bridge’s stated function. I found no install-time exfiltration, unrelated endpoint, or concealed attack behavior in the reviewed paths.
Decision evidence
public snapshot- The manifest exposes setup as an explicit command and declares no npm lifecycle hook.
- Setup reads the Telegram bot token from the package-specific environment variable or DSH credentials file.
- Setup uses that token to call Telegram’s own getMe endpoint to verify connectivity.
- The plugin starts the bridge only when configuration exists and does not disable autoStart.
- The installer’s autostart setup runs when the installer is invoked, and supports --no-autostart.
- Telegram API requests are the bridge’s documented transport for its Telegram functionality.
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.21.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.21.0 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.