dsh-tg-bridge@1.40.1
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential flows send keys to their corresponding configured services, and the setup diagnostic sends the Telegram bot token to Telegram’s API. Package scripts expose explicit commands but no install lifecycle hook was found.
Decision evidence
public snapshot- The package metadata shows no install, preinstall, or postinstall hook; its scripts are explicitly invoked commands such as setup and hooks.
- Model probes read the provider URL and key configuration, then send a short ping to that configured provider.
- Speech transcription sends the audio and configured key to the configured endpoint, defaulting to api.openai.com.
- The setup diagnostic sends the Telegram bot token to api.telegram.org for getMe, its intended Telegram service.
- The scanner flagged command execution, credential flows, and restart helpers; the inspected code uses them for bridge setup, configured provider requests, and process restarts.
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.40.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.40.1 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.