dsh-tg-bridge@1.19.12
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-aiThe high-risk scanner labels are not supported by the inspected source: the package has no install hook, provider credentials go to the configured provider, and the global persona change requires an explicit command. I found no concrete malicious behavior.
Decision evidence
public snapshot- package.json identifies the Telegram bridge entry points and has no install lifecycle hook.
- model-probe.mjs reads the active DSH provider configuration and its named key, then uses them for a minimal request to that provider after fallback failure.
- bridge.mjs runtime operation excerpts handle speech output, process diagnostics, and model probe results within the bridge flow.
- control.mjs writes the global persona section only through the explicit /soul command; without command text it displays the current value.
- The inspected panel, settings, profile, setup, and restart helpers support bridge interaction, user configuration, setup, and process management.
Source & flagged code
10 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.19.12.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.12 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.