dsh-tg-bridge@1.2.6
устаревшая сборка — ставьте 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-aiThe scanner hints point to network and child-process behavior, but inspected source ties these operations to the package’s Telegram bridge, diagnostics, and local DSH integration. No install hook or unrelated credential transfer was found.
Decision evidence
public snapshot- package.json exposes explicit commands and no npm install lifecycle hook.
- The bridge reads a DSH Telegram bot token and sends API requests to Telegram.
- Inbound messages are restricted to configured user or chat IDs, and replies go to the chat that sent the message.
- Persona changes require an explicit control command and write to the DSH agent file.
- Setup checks the Telegram bot with its token; price lookup fetches public model data with only a user-agent header.
- Inspected runtime operations process local output, manage DSH processes, update control settings, and return logs.
- The flagged network and process behavior matches the Telegram bridge, its diagnostics, and local DSH operations; no inspected source shows credentials sent to an unrelated package-selected recipient.
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.6.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.2.6 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.