dsh-tg-bridge@1.20.5
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 package has no install lifecycle hook, and its setup and startup behavior is gated by user configuration or explicit commands. The observed network request uses the configured bot token with Telegram’s own API for the package’s stated purpose.
Decision evidence
public snapshot- No npm preinstall, install, or postinstall hook is declared; setup and hooks are explicit scripts.
- The plugin starts the bridge only when a config exists, autoStart is enabled, and no bridge is already running.
- The setup probe sends the configured bot token only to Telegram’s getMe endpoint to verify connectivity.
- The CLI requires a user-supplied bot token and user ID for initialization.
- Setup uses child processes and PowerShell to manage the bridge and its scheduled task.
- The runtime reads the configured Telegram token and sends it to Telegram’s API.
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.5.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.20.5 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.