dsh-tg-bridge@1.34.1
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its flagged command execution belongs to explicit setup and maintenance tools. Credential-bearing requests target Telegram or the model and transcription endpoints configured by the user, consistent with the package's purpose.
Decision evidence
public snapshot- The manifest declares no install, preinstall or postinstall hook; setup and hook installation are explicit scripts.
- The plugin starts the bridge only when applied, a config file exists, and no bridge process is already running.
- The setup check sends the configured Telegram bot token only to Telegram’s official getMe endpoint.
- Model probes read the provider URL and key variable from the user's DSH profile, then send the key to that provider's configured API endpoint.
- Voice transcription uses a configured endpoint and API key when the user supplies audio for transcription.
- The package runs a Telegram bridge and uses configured bot and model-provider credentials, which are expected for its stated purpose.
- The setup script can restart the bridge and update a scheduled task when explicitly run.
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.34.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.34.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.