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

@alimzen/relayo-twilio

v0.1.0

Published

Twilio SMS driver for Relayo: sending through the Twilio Messages API and normalized events from its signed status callbacks and STOP replies.

Readme

@alimzen/relayo-twilio

Twilio SMS driver for Relayo: send through the Twilio Messages API and get every status (delivered, undelivered, failed) and STOP reply as normalized Relayo events.

npm install @alimzen/relayo @alimzen/relayo-twilio
import { createRelayo } from '@alimzen/relayo';
import { twilio } from '@alimzen/relayo-twilio';

const relayo = createRelayo({
  sms: twilio({
    accountSid: process.env.TWILIO_ACCOUNT_SID!,
    authToken: process.env.TWILIO_AUTH_TOKEN!,
    from: '+15550001111', // or messagingServiceSid: 'MG…'
    statusCallback: 'https://app.example.com/webhooks/relayo/sms',
  }),
});

await relayo.sms.send({ to: { address: '+34600111222' }, body: 'Your code is 482913', metadata: { userId: '42' } });
relayo.on('bounced', (event) => event.channel === 'sms' && markPhoneInvalid(event.recipient));

Webhooks

Twilio posts each message's status to statusCallback. The driver adds Relayo's message id to that URL (?relayo_message_id=…), so the events carry it, and checks Twilio's signature (X-Twilio-Signature, HMAC-SHA1 of the full URL and the parameters, keyed with your auth token). Pass the URL the request came to as req.url (the NestJS module does it for you); a path is resolved against statusCallback.

To turn STOP replies into unsubscribed events, point your number's incoming-message webhook at the same URL.

| Twilio | Relayo event | | --- | --- | | sent | accepted | | delivered | delivered | | undelivered 30005 / 30006 | bounced hard (unknown handset, landline) | | undelivered 30003, 30008 | bounced soft (unreachable, unknown error) | | undelivered 30004 / 30007 | bounced block (blocked, carrier filtering) | | failed 21610 | rejected / suppressed (the recipient replied STOP) | | failed 21211, 21612, 21614 | rejected / invalid_recipient | | failed (others) | failed | | Incoming STOP (OptOutType=STOP) | unsubscribed |

Twilio has no message metadata, so these events carry no metadata: look the message up by event.messageId. Through the Relayo platform (@alimzen/relayo-cloud), events do carry it, since the platform stores each message.

License

MIT