dsh-tg-bridge@1.19.1
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection resolved the scanner’s credential and agent-configuration indicators: the probe targets the configured provider, while commands are gated by the Telegram allowlist. The manifest has no install lifecycle hook, and no malicious behavior was identified.
Decision evidence
public snapshot- package.json lists ordinary commands and entrypoints, has no lifecycle hook or dependency, and ends without an install script.
- The probe gets its provider URL and key name from the active DSH profile or provider environment settings; on fallback errors it sends a one-token ping with that provider’s key to that provider.
- bridge.mjs sends Telegram API requests to api.telegram.org and ignores messages from user or chat IDs not in the configured allowlist.
- The agent configuration write is reached through an explicit command, and the bridge checks the configured allowlist before processing incoming messages.
- Inspected runtime operations handle DSH settings, status, logs, messages, and user-requested restarts; the profile editor performs targeted text transformations.
- The hook installer and setup or restart helpers are standalone utilities invoked by explicit commands; their inspected behavior concerns secret scanning and bridge management.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.19.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.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.