dsh-tg-bridge@1.38.5
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged command execution and credential flows fit the package’s bridge setup and configured provider features. The manifest has no install lifecycle hook, and the reviewed requests send credentials to Telegram or the provider endpoint selected by the user.
Decision evidence
public snapshot- The package declares no install, preinstall, or postinstall lifecycle script; setup and hook installation are separate commands.
- The setup probe reads the configured Telegram bot token and sends it to Telegram’s getMe endpoint to validate the token.
- Model probes send a one-token ping and the selected provider key to the provider URL read from the user’s profile.
- Voice transcription sends the audio and configured API key to the user-selected endpoint, defaulting to OpenAI’s transcription API.
- The package describes itself as a Telegram bridge and its Telegram API calls support that purpose.
- The model probe requires a configured provider and sends its key to that provider’s configured base URL.
- The setup shell and process actions manage the bridge and are invoked through an explicit setup command.
- Git hooks are created only when install-hooks.mjs is explicitly run.
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.5.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.38.5 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.