dsh-tg-bridge@1.38.4
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 only to the configured Telegram, model-provider, or transcription service. No install-time hook or unrelated credential collection was found.
Decision evidence
public snapshot- The manifest identifies a Telegram bridge and declares no install lifecycle hook.
- Setup checks the bridge’s own bot token against Telegram’s official getMe endpoint.
- Model probes use a provider URL and key source from the user’s profile or explicit environment overrides.
- Model probes send the provider key to that configured provider’s chat completions endpoint.
- The fallback probe is reached through the explicit test or x command.
- Voice transcription sends audio and its configured key to the selected transcription endpoint.
- The package includes subprocess execution for configured local transcription tools and setup tasks.
- The optional install-hooks command writes Git hooks and sets core.hooksPath when 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.4.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.38.4 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.