dsh-tg-bridge@1.7.0
устаревшая сборка — ставьте 1.11.0 или новее
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection does not substantiate the scanner’s exfiltration claim: the inspected bridge sends messages to Telegram and passes explicitly configured provider keys to the local DSH process. The global persona-file write is reachable through the explicit /soul command, and the package has no install lifecycle hook.
Decision evidence
public snapshot- package.json exposes the bridge and CLI through ordinary entry points and defines no install lifecycle hook.
- bridge.mjs reads the configured Telegram bot token and sends bridge messages to Telegram’s bot API; provider keys are passed to the configured local DSH process.
- control.mjs writes the persona section of the global instructions file only when the user invokes the /soul command with text.
- prices.mjs fetches public pricing data from the configured URL; its documented default is models.dev.
- setup.mjs and the restart helpers perform bridge setup or restart work; the restart helper waits for idle or message delivery before replacing the process.
Source & flagged code
9 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
setup.mjsView on unpkg · L19Findings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.7.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.7.0 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.