dsh-tg-bridge@1.45.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged setup request validates the user’s Telegram bot token against Telegram, while model probes and audio transcription send credentials or content to configured service endpoints for their stated features. The inspected paths do not show unrelated collection, concealed execution, or an automatic account action toward a publisher-chosen target.
Decision evidence
public snapshot- The manifest describes a DeepSeek Harness to Telegram bridge.
- The setup command reads the Telegram bot token and checks it with Telegram’s own getMe endpoint.
- Model probes read the provider URL and key variable from the active DSH profile, then send a one-token ping to that provider.
- Voice transcription sends audio and its configured key to the configured speech endpoint.
- The inspected setup network request targets api.telegram.org, consistent with the bridge’s stated purpose.
- The model probe uses the provider URL and key variable configured in the DSH profile.
- Voice transcription is invoked for audio messages and uses the configured voice endpoint.
Source & flagged code
10 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.45.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.45.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.