dsh-tg-bridge@1.19.6
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection resolved the scanner’s credential and agent-configuration indicators as provider-aligned diagnostics and a command-based control feature. The manifest declares no install lifecycle hook, and the inspected source did not establish a concrete attack.
Decision evidence
public snapshot- The manifest identifies a Telegram bridge entrypoint and ordinary named commands; no npm lifecycle hook is declared.
- The model probe reads a key from the selected DSH provider profile and sends it as a bearer credential to that provider’s configured base URL with a one-token ping.
- The `/soul` command writes the supplied persona text to the agent file; bridge updates pass through an allowed-sender check, and the helper accepts configured user or chat IDs.
- The inspected control, panel, and settings operations implement bridge commands, display settings, and profile controls; no independent attack behavior was identified in those paths.
- The install-hook helper is an explicit command for installing secret-scan Git hooks; setup and restart helpers describe bridge maintenance actions.
- No unconsented install-time mutation, unrelated credential recipient, or concrete malicious behavior was found in the inspected source.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.19.6.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.6 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.