dsh-tg-bridge@1.28.0
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential flow sends a small health-check request to the provider selected in the user’s profile, while setup’s bot-token request goes to Telegram’s API. Command execution and file changes are associated with explicit setup or hook commands, and the package declares no install lifecycle hook.
Decision evidence
public snapshot- The package exposes setup as an explicit npm command; its metadata shows no install lifecycle hook.
- Model probes take the host and API-key variable from the configured provider profile, with environment overrides for debugging.
- A probe sends a one-token “ping” request with the key to that provider’s `/chat/completions` endpoint.
- Setup’s `getMe` request uses the Telegram API with the bot token to check connectivity after a restart.
- The package reads credentials and performs network requests during provider probes, but the destination comes from the configured provider profile.
- Setup and hook utilities execute local commands and write files, but they are exposed as explicit commands rather than install hooks.
Source & flagged code
9 flaggedSource executes local commands and sends command output to an external endpoint.
setup.mjs#virtual:normalized:round1View on unpkg · L107Findings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.28.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.28.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.