dsh-tg-bridge@1.2.10
устаревшая сборка — ставьте 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 11d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner’s exfiltration claim. The manifest has no install hook, and the observed network and configuration actions are consistent with explicit bridge use and setup.
Decision evidence
public snapshot- package.json has no install lifecycle hook; it exposes bridge startup and setup as explicit commands.
- The bridge sends Telegram API requests to api.telegram.org and runs the configured DSH command for chat tasks; no unrelated credential recipient was found.
- Only configured Telegram user or chat IDs reach message handling. The /soul command writes the persona section of ~/.dsh/AGENTS.md when requested.
- Setup performs service maintenance and a Telegram getMe check when explicitly run.
- The inspected runtime-operation locations handle transcription and error output, explicit plugin or app controls, language selection, and log display.
- The high-risk scanner labels are not supported by the inspected source: the network destination is Telegram, setup is user-invoked, and no install hook appears in the manifest.
Source & flagged code
5 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.2.10.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.2.10 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.