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

@entropyinternet/alertsboo-helpers

v0.1.18

Published

This package contains types and helper functions for the Alerts Boo project.

Readme

Alerts Boo Helpers & Types

This package contains types and helper functions for the Alerts Boo project.

Usage

$ npm install --save @entropyinternet/alertsboo-helpers
import type { Alert } from '@entropyinternet/alertsboo-helpers';

Update Version

$ npm install --save @entropyinternet/[email protected]

Building

Every npm release must update the version number in package.json.

$ yarn install
$ yarn build
$ npm publish --access public

Billing Patterns

We use DynamoDB for tracking billable events.

Credits Based Billing

We sell credits to customers as a simplified way to measure usage. Our actual expense per credit is a blend of costs. Our profit margin will fluctuate based on the price we sell credits at.

We use DynamoDB to track both the blend of costs, and the credits.

1 credit = blend of costs (~$0.01 expense)
PriceA = 100 credits sold for $10 (90% profit)
PriceB = 1000 credits sold for $70 (85% profit)

Session Based Billing

We report credit usage to customers by the "run" aka "session". For example, customer is watching an Instagram account for updates. If that account posts a new story, the run session looks like this:

  1. Volunteer Android relays the push notification to our webhook listener
  2. Listener retrieves IG data from RapidAPI vendor (expense)
  3. Listener attributes earnings to volunteer (expense)
  4. Listener uses Ai credits (expense)
  5. Listener costs cloud resources (expense)
  6. Other misc variable costs related to this run (expense)

The entire timeline of events is a "run". We use DynamoDB to track the costs of each run. The "sessionID" is the unique identifier for the run.

At each expense, we report the cost to DynamoDB.

But the run isn't done yet. There is still more accounting to do:

  1. Calculate the cost of run and translate to credits
  2. Report N credits consumed to DynamoDB
  3. Reflect the updated balance in customer's wallet

And costs don't directly translate 1:1 from to a run. Some costs are shared "batch" costs. However for simplicity we get customers to pay credits the entire cost of batch. Thus do not use credits as a reflection of margins (margins will tend to be higher).