dsh-tg-bridge@1.19.5
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 found no npm lifecycle hook or unrelated credential recipient. The probe sends a minimal request to the provider selected by the active profile or explicit environment configuration, while bridge controls are subject to the configured user and chat allowlist.
Decision evidence
public snapshot- The manifest has no npm lifecycle hook; setup and repository hook installation are explicit commands.
- On a recovery path, the bridge probes a provider URL from the active DSH profile or its environment override, using that provider’s configured key and a one-token test request.
- Telegram requests go to api.telegram.org, and incoming messages are ignored unless the sender or chat is configured as allowed.
- The persona file is changed by the chat command that supplies its new text; the bridge applies the configured user and chat allowlist before processing messages.
- The inspected control operations modify DSH settings or manage its plugins and process; they do not establish an unrelated credential transfer.
- The plugin starts the bridge only when its configuration exists, unless auto-start is disabled.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.19.5.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.5 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.