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

mxby-statgenerator

v1.0.4

Published

Generates stats reports for Mixby applications

Readme

STAT GEN

This app is intended to generate and maintain stats reports for Mixby applications A stat report is an object which contains relevant stat totals for a given beacon or place It requires a loopback app with a mongo database and the current mixby data model

It typically looks like this:

Stat = {
   beaconId: [objectId] id of the beacon this stat report relates to
   endDate: [date] end of day in utc relative to the location of the beacon (or the beacon's parent place)
    popularityIndex: [float] number indicating popularity of the beacon as a whole (measure of interactions + visits + time spent etc
    totalVisits: [int] how many times the beacon was entered
    totalUniqueVisits: [int] how many people visited the beacon
    averageTimeSpentInMinutes: [int] average minutes spent at the beacon
    totalArtifactsCollected: [int] total number of artifacts collected from this beacon
    totalArtifactsViewed: [int] total number of view stats for artifacts
    averageTimeSpentViewingArtifactsInMinutes: [int] average minutes spent viewing artifacts
    totalChallengesCollected: [int] total number of artifacts collected from this beacon
    totalChallengesViewed: [int] total number of view stats for artifacts
    totalChallengesCompleted: [int] total number of view stats for artifacts
    averageTimeSpentViewingChallengesInMinutes: [int] average minutes spent viewing artifacts
    totalExtrasCollected: [int] total number of artifacts collected from this beacon
    totalExtrasViewed: [int] total number of view stats for artifacts
    averageTimeSpentViewingArtifactsInMinutes: [int] average minutes spent viewing artifacts
    beaconsCameFrom: [array][obj] {beaconName: str, beaconId: objectId, count: int}
    beaconsWentTo: [array][obj] {beaconName: str, beaconId: objectId, count: int}
    mostPopularArtifacts: [array][obj] {artifactId: objectId, views: int, collections: int}
    mostPopularFunFacts: [array][obj] {funFactId: objectId, views: int, collections: int}
    mostPopularQuizzes: [array][obj] {quizId: objectId, views: int, collections: int, completions: int}

}

How To:

npm install mxby-statgenerator
(and all loopback server requirements)

var app = require('../server')
var SG = require('mxby-statgenerator')
var sg = new SG(app)
sg.generateDailyReport(beacon, Date, function(err, statsReport){
  statsReport is a statReport Object from the database
})

TODO:

  • add methods to support reports for individual items - these methods should add stats to the object and save it to the database
  • a beacon should only have 1 stat report per day -- the generator needs to check this first -- their should be a flag to set to override this
  • helper methods to support retrieving beacon stats for a given time period -- though the idea is that you can do this with just a generic StatsReport query