dsh-tg-bridge@1.32.0
Telegram bridge for [DSH]: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged setup and process execution are part of user-invoked bridge management, and no install hook is declared. The credential flow inspected is directed to Telegram or the provider configured for model requests, consistent with the package’s purpose.
Decision evidence
public snapshot- The manifest declares start, setup, check, and other user-invoked scripts; it has no install lifecycle hook.
- Setup’s connectivity check sends the configured bot token to Telegram’s getMe endpoint.
- The new endpoint handler acts only on an explicit /endpoint command and applies changes to the active profile.
- Endpoint URLs must use HTTPS, except for localhost HTTP.
- Model probes send a one-token ping and the profile’s configured API key to that provider’s /chat/completions endpoint.
- Plugin startup is conditional on configuration being present and can be disabled with autoStart: false.
- Setup can stop and restart bridge processes and register a scheduled task when explicitly run.
- Model probing reads configured provider credentials and sends them to the endpoint chosen in the profile.
Source & flagged code
10 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.32.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.32.0 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.