dsh-tg-bridge@1.24.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 command execution and environment access support explicit bridge setup, while the token is used for a Telegram API check. No unrelated collector or harmful automatic action was found.
Decision evidence
public snapshot- The manifest declares a plugin entry point and CLI; setup is an explicitly invoked npm script, with no lifecycle hook declared.
- Setup reads the Telegram bot token from its intended environment variable or credentials file.
- Setup uses the token to call Telegram’s own api.telegram.org getMe endpoint as a connectivity check.
- The plugin starts the bridge only after configuration exists and no bridge process is already running.
- The bridge restart command requires the explicit argument `restart confirm`.
- Setup stops and restarts bridge processes, updates a scheduled task, and installs a Telegram bot menu when the user runs setup.
- The package accesses the network and credentials for its Telegram bridge function.
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.24.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.24.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.