npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@open-neko/channel-telegram

v0.4.0

Published

Telegram channel for OpenNeko: delivers the agent's Briefing, findings, and approvals to a Telegram chat, and turns replies + inline-button taps back into agent intents. Bidirectional. Runs in a microsandbox VM with network egress limited to api.telegram.

Downloads

875

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

amitdeshmukhamitdeshmukh

Keywords

Readme

@open-neko/channel-telegram

A channel for OpenNeko — a frontend, like Slack or the built-in web app, but talking to a Telegram chat. It is bidirectional: it delivers the agent's Briefing, findings, and approvals to a chat, and turns replies and inline-button taps back into agent intents.

Unlike an action plugin (which the agent calls to do one thing), a channel sits at the Interaction Protocol waist: the agent emits modality-free InteractionEvents for an audience, and this plugin projects them into Telegram's native shape inside its sandbox VM.

What it does

| RPC | Direction | Behaviour | |---|---|---| | deliver | OpenNeko → Telegram | Projects InteractionEvent[] → sendMessage calls (HTML; an ask becomes an inline keyboard). | | parse_inbound | Telegram → OpenNeko | Normalizes a Telegram Update (button tap / message / /command) → IntentEvent[]. | | verify_inbound | Telegram → OpenNeko | Constant-time check of the X-Telegram-Bot-Api-Secret-Token webhook header. |

The capability profile it declares: text modality, Markdown, inline buttons (interactiveControls + canApproveInline + quickReplies), 4096-char limit, push attention — richer than WhatsApp, leaner than the web dashboard.

Setup

  1. Create a bot with @BotFather → get the bot token.
  2. Install the channel and set the token:
    openneko install @open-neko/channel-telegram
openneko secrets set @open-neko/channel-telegram TELEGRAM_BOT_TOKEN 123456789:AA…
  3. Inbound — either:
    • Long-poll (no public URL): a worker-side poller calls getUpdates and feeds each Update to parse_inbound; or
    • Webhook: register https://<deployment>/channels/@open-neko%2Fchannel-telegram/inbound with a secret_token, and set TELEGRAM_WEBHOOK_SECRET to the same value so verify_inbound can authenticate it.

Dry-run

If TELEGRAM_BOT_TOKEN is unset at exec time, deliver still projects the payload and writes it to stderr, returning { delivered: false, ref: "dry-run:N" } — so the projection can be exercised locally with no bot and no network.

Network

Egress is limited to api.telegram.org by the manifest; the sandbox blocks everything else.