dsh-tg-bridge@1.7.1
устаревшая сборка — ставьте 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 found no lifecycle hook or package-controlled credential recipient. The flagged process and network operations support explicit setup, local harness turns, authorized Telegram controls, and price lookup.
Decision evidence
public snapshot- package.json has no install lifecycle hooks; its scripts run the bridge or setup only when explicitly invoked.
- The bridge reads its Telegram bot token from DSH credentials or the environment and sends Bot API requests to Telegram.
- Incoming messages are checked against configured user or chat IDs before processing; turns run through the local DeepSeek Harness CLI.
- Provider keys are read only when their names are listed in configuration and are passed to the local harness process.
- Persona-file changes occur in response to the explicit /soul command, and authorized-user checks precede message handling.
- The price lookup uses models.dev by default; a separate provider page is optional configuration.
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.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.7.1 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.