dsh-tg-bridge@1.38.3
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged credential flows send keys to the services they are configured for, and setup’s token check targets Telegram. Package startup is part of the bridge’s stated function and is gated on initialization; no unrelated collection or malicious behavior was found.
Decision evidence
public snapshot- The package describes a Telegram bridge and declares no npm lifecycle scripts; its main entry is plugin-bridge.mjs.
- Model probes use the provider key and base URL selected from the configured profile, with optional explicit environment overrides.
- Voice transcription sends audio and its configured key to the configured transcription endpoint.
- Setup validates the bot token with Telegram’s getMe endpoint, and the plugin waits for initialization to create config.json before starting the bridge.
- The bridge’s network and process activity serve its stated Telegram integration and configured model or transcription features.
- No unrelated credential destination or install-time data collection was identified.
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.3.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.38.3 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.