registry / @wienerberliner/pi-telegram / 0.1.6

@wienerberliner/pi-telegram@0.1.6

One-way Telegram notifications for Pi agents via a BotFather bot.

AI Security Review

scanned 15h ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. A Pi extension registers Telegram notification tools at package load. Its explicit setup command stores a BotFather token and chat ID in its own global Pi extension config, and tool calls can upload caller-selected content.

Static reason

No blocking static signals were detected.

Trigger

Pi loads the declared extension; network/file actions require a Telegram tool call or `/setup-telegram-token`.

Impact

Configured Pi sessions gain a user-invoked outbound Telegram channel for selected text and files.

Mechanism

First-party Pi extension setup plus Telegram Bot API notification/upload tools.

Rationale

Source shows a legitimate but sensitive first-party agent extension with explicit configuration persistence and outbound file/message capability. There are no install hooks or stealth/exfiltration behavior beyond the declared Telegram functionality.

Evidence

package.jsonextensions/telegram.tsbin/pi-telegram.mjsskills/telegram-notify/SKILL.md~/.pi/agent/pi-telegram/.env<Pi current working directory>/.env<caller-selected local media file>

Network endpoints1

api.telegram.org

@wienerberliner/pi-telegram@0.1.6

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code