dsh-tg-bridge@1.41.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged credential flows send credentials to Telegram or the provider configured for the related feature. The command execution and network activity reviewed are consistent with the package’s stated bridge and setup purpose.
Decision evidence
public snapshot- The manifest declares start and utility scripts, with no preinstall, install, or postinstall hook.
- When setup runs, it checks the supplied Telegram bot token against Telegram’s getMe endpoint.
- Model probes read the selected provider URL and key from profile settings or explicit environment overrides, then send a one-token ping to that URL.
- Voice transcription uses a configured speech endpoint and key to transcribe an incoming Telegram audio attachment.
- The package has network and process-execution capabilities, including bridge startup and restart management, consistent with its Telegram bridge purpose.
- The setup check contacts Telegram and sends the bot token, but only to api.telegram.org. Voices and model requests may send configured credentials and user-provided content to their selected providers.
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.41.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.41.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.