dsh-tg-bridge@1.38.8
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner’s command execution and credential-flow alerts resolve to bridge setup, restart, model probing, and configured voice transcription behavior. The inspected manifest has no install lifecycle hook, and the flagged paths show no unrelated collection or exfiltration.
Decision evidence
public snapshot- The manifest identifies the plugin and CLI entry points and lists user-invoked commands; it declares no preinstall, install, or postinstall script.
- The model probe obtains a provider key and sends it to that provider’s configured base URL for a model availability check.
- Voice transcription sends the audio and configured API key to the voice provider’s configured endpoint.
- The setup command uses the Telegram bot token with api.telegram.org to call getMe as a connectivity check.
- The plugin starts the bridge only when configuration exists, and can be disabled with autoStart=false.
- No credential or command output is sent to an unrelated collector in the inspected flagged paths.
- The credential-bearing requests target configured provider endpoints or Telegram, matching the package’s bridge and model-probing purpose.
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.38.8.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.38.8 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.