dsh-tg-bridge@1.30.1
identical to 1.30.2; use 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 command execution is used for local diagnostics and bridge management, while network requests go to Telegram or the provider URL configured by the user. The manifest has no lifecycle hooks, and the inspected startup path requires bridge configuration.
Decision evidence
public snapshot- The package describes itself as a Telegram bridge for DeepSeek Harness.
- The plugin starts the bridge only after configuration exists and a token has been set up.
- The model probe uses the provider base URL and key environment variable from the user's profile or explicit overrides.
- Setup's network check calls Telegram's getMe endpoint using the configured bot token.
- No lifecycle scripts are declared in the package manifest.
- The flagged setup commands inspect local process and disk state and manage the bridge; they do not send command output to an unrelated host.
- The installer configures autostart as part of an explicitly run install script.
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.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.30.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.