dsh-tg-bridge@1.19.2
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 shows the credential-bearing request targets the active provider configured for the bridge and is used as a fallback health probe. The manifest has no npm install hook, and the inspected control-surface write is invoked by `/soul`; the scanner’s flagged runtime operations resolve to ordinary bridge behavior.
Decision evidence
public snapshot- The manifest defines no npm install lifecycle hook; Git hooks are installed through a separate command. The inspected setup and restart helpers perform Telegram setup or bridge maintenance.
- The model probe reads a key named by the active provider profile and sends a one-token health request to that provider’s configured base URL. The bridge calls it only after model fallback failures.
- The inspected bridge operations handle Telegram requests, process output, model-fallback status, and idle or post-send restarts.
- The flagged control operations are user-facing bridge commands for settings, application control, language, and status. The global persona write is reached through the explicit `/soul` command and only replaces its named persona section.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.19.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.2 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.