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

@mulmobridge/viber

v0.1.1

Published

Viber bridge for MulmoBridge — Public Account chatbot via webhook + REST

Downloads

28

Vulnerabilities

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

Links

Maintainers

isamuisamusnakajimasnakajima

Keywords

Readme

@mulmobridge/viber

Experimental — please test and report issues.

Viber Public Account chatbot bridge for MulmoClaude. Receives user messages via HTTPS webhook, replies via the Viber Bot REST API. Popular in Eastern Europe, Southeast Asia, and parts of the Middle East.

Public URL required (Viber only supports webhook delivery).

Setup

1. Create a Public Account (Bot)

  1. Open Viber app → More → Public Accounts → Create Account.
  2. Complete the onboarding; pick a category.
  3. On the admin panel (partners.viber.com) → Your Account → Edit Info → Chatbot / Subscribe Bot → copy the Authentication Token.

2. Expose the bridge

ngrok http 3012
# → https://abcd.ngrok-free.app

3. Set the webhook

Once you have the public URL, register it with Viber. Either via the admin panel, or via a one-off HTTP call:

curl -X POST https://chatapi.viber.com/pa/set_webhook \
  -H "X-Viber-Auth-Token: <VIBER_AUTH_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://abcd.ngrok-free.app/viber","event_types":["message"]}'

4. Run the bridge

VIBER_AUTH_TOKEN=... \
npx @mulmobridge/viber

Send a message to your Public Account from the Viber app — you'll get a reply.

Environment variables

| Variable | Required | Default | Description | |------------------------|----------|-----------------|-------------| | VIBER_AUTH_TOKEN | yes | — | Public Account auth token from the admin panel | | VIBER_SENDER_NAME | no | MulmoClaude | Display name used on outbound messages | | VIBER_WEBHOOK_PORT | no | 3012 | HTTP port | | VIBER_ALLOWED_USERS | no | (all) | CSV of Viber user IDs allowed (empty = everyone who messages the bot) | | MULMOCLAUDE_AUTH_TOKEN | no | auto | MulmoClaude bearer token override | | MULMOCLAUDE_API_URL | no | http://localhost:3001 | MulmoClaude server URL |

How it works

  1. Viber POSTs event JSON to /viber with an X-Viber-Content-Signature header (HMAC-SHA256 of the raw body keyed on the auth token).
  2. The bridge verifies the signature in constant time and ACKs 200 immediately so Viber doesn't retry.
  3. For event:"message" with message.type === "text", the bridge runs the allowlist, then forwards message.text to MulmoClaude keyed by sender.id.
  4. Replies go out via POST /pa/send_message with the auth token in the X-Viber-Auth-Token header. Chunked at 7 000 chars.

Troubleshooting

| Symptom | Cause | Fix | |---|---|---| | Webhook registration returns {"status":10,"status_message":"No URL parameter supplied."} | Typo in set_webhook call | Re-check JSON body | | Invalid signature on all events | Rotation mismatch between VIBER_AUTH_TOKEN and the token used to register the webhook | Re-register the webhook using the current token | | send non-zero status: {"status":6,…} | Receiver hasn't messaged your bot first | Viber requires the user to start the conversation before you can push to them |

Security notes

  • The auth token is both the bot's identity and the webhook signing key — rotate it via the admin panel if it leaks.
  • VIBER_ALLOWED_USERS is recommended. Without it, anyone who finds your Public Account can chat with your agent.
  • Viber's chat history is controlled by the Viber app — the bridge itself keeps no local message log.

Ecosystem

Part of the @mulmobridge/* package family.

Shared libraries:

Bridges (one npm package per platform):