dsh-tg-bridge@1.6.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-aiThe apparent data-transfer behavior is the bridge’s expected Telegram message handling, restricted to configured user or chat IDs. The manifest has no install lifecycle hook, and the inspected agent configuration change is explicitly user-invoked.
Decision evidence
public snapshot- package.json lists no install lifecycle hook; setup and restart helpers are separate commands.
- The bridge sends through Telegram’s API and ignores messages unless the sender or chat is in the configured allowlist.
- The agent persona file is changed only through the explicit /soul command, after the bridge’s message authorization check.
- The optional price lookup uses the public models.dev catalog by default.
- Setup and restart helpers perform bridge health and restart operations.
Source & flagged code
8 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.6.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.6.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.