dsh-tg-bridge@1.40.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 network and process behavior is part of the bridge's intended Telegram, model-probe, and transcription functions. Credentials are sent to the corresponding Telegram or configured provider endpoint, and setup is an explicit CLI command.
Decision evidence
public snapshot- package.json declares no install lifecycle hook; its scripts are explicit commands such as setup and hooks.
- Audio transcription uses a configured endpoint and key when processing a Telegram audio message.
- Model probes use the provider URL and key environment variable from the active DSH profile, or explicit probe overrides, and send a one-token ping.
- The setup command is invoked through the CLI and its token check calls Telegram's own getMe endpoint.
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.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.40.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.