dsh-tg-bridge@1.13.2
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 install lifecycle hook or concrete attack behavior. The flagged agent configuration write is an explicit /soul command behind the allowed-user check, and the bot token is used for Telegram API operations.
Decision evidence
public snapshot- package.json exposes explicit start and setup commands; it declares no install lifecycle hook.
- Telegram commands are limited to configured allowed users, and /soul writes the global persona only when explicitly invoked with text.
- Bridge bot requests go to Telegram's API, and its token is used to operate that bot.
- The plugin handler processes explicit plugin actions; profile edits are described as user-set configuration.
- The price catalog uses models.dev; setup and restart helpers describe explicit setup and reply-safe restart behavior.
- Panel code formats turn output; the reviewed runtime operation locations do not establish an attack.
- When invoked, install-hooks.mjs writes pre-commit and pre-push hook files under .githooks.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.13.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.13.2 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.