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

opscms-analytics-plugin

v1.0.3

Published

Per-site analytics for an OpsCMS platform: each site's own Google, Matomo, Plausible, Fathom, Umami, PostHog or custom settings, and the server-side GA4 workflow action.

Readme

opscms-analytics-plugin

Per-site analytics for the OpsCMS platform, built with opscms-sdk.

  • analytics-integrations: each site's own analytics providers: Google (GA4 and Tag Manager), Matomo, Plausible, Fathom, Umami, PostHog, or a custom script. A site can run several at once. The server secret (GA4's Measurement Protocol secret) is encrypted under the site's key and shown masked; the platform's public content API never returns it. A custom script is injected verbatim into every page of the site, so only the platform owner may write one.
  • The ga4-send-event workflow action: carries out the platform's send_analytics_event block, sending a server-side event to GA4 with the site's own measurement id and secret. A site with no active GA4 setup is skipped successfully: tracking is best-effort and never fails the business workflow.

Meta's own server-side events belong to the Meta plugin (meta-conversion-event), not to this one.

Install

From the admin: Plugins → Install from npm → opscms-analytics-plugin. The platform creates the plugin's table (its one migration), lists the plugin with its logo, and restarts to start it. Removing the plugin drops its table and the secrets in it.

The platform currently carries this plugin in its own code under the same key; install the package only after that copy has been removed. The platform's public content API serves this collection to a site's storefront by its slug, analytics-integrations.

Needs

payload ^3 and opscms-sdk ^0.1.7 (the platform provides both).

Develop

npm install
npm run typecheck && npm test && npm run build && npm pack --dry-run

opscms-sdk is linked from a sibling checkout (file:../opscms-sdk) until it is published.