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

@telegraph-notify/telegraph-dashboard

v1.0.0

Published

Dashboard to observe Telegraph metrics.

Readme

Telegraph Dashboard

The dashboard is a centralized location for visualizing your Telegraph service implementation and an observability tool for monitoring system health.

Features

  • View notification status and filter notification requests by recipient ID or channel.
  • View users and filter by User ID, Email, or notification preferences.
  • Visualize system activity and performance with charts displaying:
    • Successful and failed notification deliveries.
    • Notification deliveries by channel.
    • Notification failures by channel.
  • Inspect messages which failed processing and were diverted to the service's dead letter queue.

Installation

To install the dashboard, run the following command:

$ npx @telegraph-notify/telegraph-dashboard

This will create a subdirectory named telegraph-dashboard. Navigate to this directoy and run:

$ npm install

To initialize the dashboard server, a .env file must be created with the following information:

| Key | Value | | ----------------- | ---------------------------------------------------------------------------------------- | | VITE_HTTP_GATEWAY | URL of the HTTP API Gateway. This is output by Telegraph CLI after depolyment. | | VITE_API_KEY | The API key to access the HTTP Gateway. This is set during Telegraph CLI initialization. |

Please refer to Telegraph CLI for more information.

Usage

Running the Dashboard

The dashboard is intended to be run on localhost by a trusted entity. Run the following command to start the dashboard:

$ npm run prod

The server listens for connections on port 5173 and can be viewed from a browser at localhost:5173/.

Interpreting Notification Logs

Notification logs are generated so developers can extract metrics from Telegraph if desired and as an observability tool. When a notification failure occurs, the dashboard attaches a failure badge to the log. The following table maps logs to their lambda's so users can understand where in the system to start debugging.

| Lambda | Logs | | :------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------- | | sendEmail | Email sent.Email could not be sent: SES failure.Error sending email. | | sendSlack | Slack notification sent.Slack notification could not be sent.Error sending slack notification. | | dynamoLogger | Notification request received.Notification not sent - channel disabled by user. | | sendInitialData | In-app notification sent. | | updateNotification | In-app notification read.In-app notification deleted. | | websocketBroadcast | In-app notification sent.In-app notification queued for sending.In-app notification unable to be broadcast. |