dsh-tg-bridge@1.46.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged command execution is used for local diagnostics, process supervision, and restart tasks. Credential-bearing requests go to the configured model or transcription service, while the Telegram check uses the configured bot token with Telegram’s API; no unrelated exfiltration was identified.
Decision evidence
public snapshot- The package describes a Telegram bridge and exposes a plugin entry point for that purpose.
- The model probe sends a short ping to the configured provider base URL using that provider’s configured key.
- Audio transcription sends the audio file to the configured transcription endpoint as part of the feature.
- Setup contacts Telegram’s official API using the configured bot token for a getMe check.
- Setup and the supervisor use child processes and local process management, consistent with the documented bridge restart and health-check functions.
- The supervisor starts the bridge only when it is not already running; the plugin waits until initialization has written a token and working directory.
Source & flagged code
10 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.46.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.46.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.