dsh-tg-bridge@1.2.7
устаревшая сборка — ставьте 1.11.0 или новее
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no npm install lifecycle hook, unrelated credential transfer, or unrequested account action. The flagged setup network request verifies the Telegram bot token with Telegram, while persona changes require an explicit command from an allowed user.
Decision evidence
public snapshot- package.json defines user-run scripts and no npm lifecycle hook or runtime dependency.
- bridge.mjs reads a Telegram bot token, sends requests to api.telegram.org, and filters incoming messages by allowed user IDs.
- setup.mjs uses the configured Telegram token for a getMe verification request to api.telegram.org.
- The /soul command writes supplied text to the DSH persona file; it is an explicit command behind the bridge’s user-ID filter.
- Inspected runtime snippets cover transcription and CLI output handling, plus user-invoked plugin, restart, stop, language, and log controls; they show no hidden account action.
Source & flagged code
5 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
setup.mjsView on unpkg · L19Findings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.2.7.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.2.7 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.