dsh-tg-bridge@1.30.2
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential flow sends the configured provider key to the base URL selected in the user's DSH profile, and setup checks the bot token with Telegram. The package has no npm lifecycle scripts, and plugin startup requires bridge configuration.
Decision evidence
public snapshot- The package describes itself as a Telegram bridge and declares no npm lifecycle hooks.
- Model probes use the provider base URL and API key configured in the user's DSH profile or explicit probe overrides.
- The plugin starts the bridge only when configuration exists and no instance is already running.
- The setup check sends the configured bot token to Telegram's own getMe endpoint.
- The package runs child processes and installs autostart through explicit setup or installer commands.
- The bridge handles Telegram and model-provider credentials as part of its stated 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.30.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.30.2 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.