dsh-tg-bridge@1.15.1
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks or dependencies, and the inspected runtime behavior aligns with the Telegram bridge’s stated purpose. Scanner labels and similarity hints did not establish an attack in the source reviewed.
Decision evidence
public snapshot- package.json defines no lifecycle hooks or dependencies; it exposes a Telegram bridge entrypoint and user-run commands.
- bridge.mjs sends API requests to Telegram using the configured bot token, consistent with the package’s stated bridge purpose.
- control.mjs writes the persona section of the global instructions file only when the /soul command receives text; the reviewed control operations handle user-requested settings, process control, and status display.
- The flagged bridge and panel excerpts process transcription output and format status text; they do not establish credential exfiltration.
- The helper scripts describe explicit setup or bridge restart behavior, and no reviewed source establishes an install-time attack.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.15.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.15.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.