dsh-tg-bridge@1.2.5
устаревшая сборка — ставьте 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 found no install lifecycle hook or concrete attack behavior. The flagged network and agent configuration code serves the package's bridge, pricing, and explicit command functions.
Decision evidence
public snapshot- package.json declares the bridge and CLI entrypoints, has no lifecycle hook, and lists no dependencies.
- bridge.mjs sends bot requests to Telegram; setup.mjs checks the configured bot token with Telegram's getMe endpoint.
- The other external requests fetch public model pricing data, called by the explicit /prices command.
- control.mjs writes the DSH instructions file only when a /soul command supplies text.
- Inspected runtime handlers process transcription and CLI output, and implement explicit plugin, restart, stop, and language commands.
- Static hints allege runtime exfiltration and risky agent configuration changes, but the inspected network calls serve Telegram or requested price lookups, and the instructions-file write is command-triggered.
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.5.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.2.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.