dsh-tg-bridge@1.25.3
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 is used for local bridge setup and restart, while the inspected network calls target Telegram or the provider configured by the user. The model key is sent to that configured provider for a minimal health probe, and there is no install lifecycle hook.
Decision evidence
public snapshot- Package metadata lists setup and start commands but no install lifecycle hook; the main entry is the bridge plugin.
- The plugin starts the bridge only when configuration exists and autoStart has not been disabled.
- Model probes obtain the provider URL and key variable from the active profile, with environment overrides for debugging.
- A model probe sends the key as a bearer token to that configured provider’s chat completions endpoint with a one-token ping.
- Setup’s network probe calls Telegram’s official getMe endpoint using the bot token to verify connectivity.
- Setup and restart helpers execute local process-management commands, but their inspected code uses them to manage the bridge and scheduled task.
- The flagged restart helpers wait for an idle state or a delivered reply before restarting the bridge.
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.25.3.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.25.3 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.