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

@xurizaemon/hubot-matrix

v3.0.2

Published

Matrix adapter for Hubot

Vulnerabilities

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

Links

Maintainers

xurizaemonxurizaemon

Keywords

Readme

Hubot adapter for Matrix

This is a Hubot adapter for Matrix.

Installation

Use the following adapter based on your Hubot version (npm list hubot).

  • For Hubot v2, npm i hubot-matrix@1
  • For Hubot v3, npm i hubot-matrix@2
  • For Hubot v13+, npm i @xurizaemon/hubot-matrix

Adapter configuration

Set the following variables:

  • HUBOT_ADAPTER should be @xurizaemon/hubot-matrix
  • HUBOT_MATRIX_HOST_SERVER - the Matrix server to connect to (default is https://matrix.org if unset)
  • HUBOT_MATRIX_USER - bot login on the Matrix server - eg @examplebotname:matrix.example.org
  • HUBOT_MATRIX_PASSWORD - bot password on the Matrix server

Tests

To run tests in Github Actions, the following Github Secrets should be configured.

| Name | Example | Description | |------------------------|----------------------------------|---------------------------| | TEST_MATRIX_URL | https://matrix-client.matrix.org | Home instance URL | | TEST_MATRIX_ROOM | !something:example.org | Room ID (where to get it) | | TEST_MATRIX_USER | @someuser:example.org | Username | | TEST_MATRIX_PASSWORD | ******** | Password |

There are environment variables which the tests need set to execute also. In Github Actions, these variables are set in the Github workflow configuration (.github/workflows/*.yml).

| Name | Example | Description | |-------------------------|----------------------------------|----------------------------| | HUBOT_MATRIX_HOST | https://matrix-client.matrix.org | Home instance URL | | HUBOT_MATRIX_PASSWORD | **** | Test user a/c password. | | HUBOT_MATRIX_USERNAME | **** | Test user a/c login. | | HUBOT_FAREWELL_* | Configure hubot-farewell^1 | Configure shutdown message | | HUBOT_STARTUP_* | Configure hubot-startup^2 | Configure startup message |

Jest requires the experimental-vm-modules Node option to run .mjs tests:

NODE_OPTIONS="$NODE_OPTIONS --experimental-vm-modules" npm run test

Releasing

Will this work? We have an NPM and GPR publish workflow lol.

  1. Update version in package.json (and package-lock.json)
  2. Commit these changes
  3. Create a Git tag matching the version
  4. Push commits and tags
  5. Create a GitHub release based on the tag (which will trigger your workflow)