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

@matvi-consulting/monitoring-agent-cloud

v0.2.0

Published

Pulumi components deploying the Matvi monitoring agent on AWS ECS Fargate and Azure Container Apps

Readme

monitoring-agent-cloud

Agent de monitoring Matvi pour les plateformes managées sans hôte : AWS ECS Fargate et Azure (App Service, Container Apps).

Un conteneur unique, déployé chez le client, interroge CloudWatch (YACE) ou Azure Monitor (azure-metrics-exporter) avec des droits en lecture seule, et pousse les métriques vers la push gateway Matvi. Aucun log n'est collecté.

  • Image : ghcr.io/matvi-consulting/monitoring-agent-cloud
  • Composants Pulumi : @matvi-consulting/monitoring-agent-cloud, un sous-chemin par fournisseur pour n'installer que le peer utilisé :
    • import { MatviMonitoringAws } from "@matvi-consulting/monitoring-agent-cloud/aws" (peer @pulumi/aws)
    • import { MatviMonitoringAzure } from "@matvi-consulting/monitoring-agent-cloud/azure" (peer @pulumi/azure-native)
    • la racine n'exporte que la partie commune (agentImage, agentEnvironment, ...)
  • Installation : AWS, Azure
  • Design : spec

Développement

./tests/run.sh            # tests bats (Docker requis)
./tests/image-smoke.sh    # build + vérifications de l'image
cd pulumi && npm test     # tests des composants

Release

./release.sh : tag vX.Y.Z, puis la CI publie l'image et le package npm à la même version (après les tests bats et Pulumi).

Checklist avant le premier déploiement client :

  • [ ] Visibilité du package GHCR monitoring-agent-cloud passée en Public (GitHub → Packages → monitoring-agent-cloud → Package settings → Change visibility). Un package GHCR est privé à sa première publication : sans cela, ECS et Container Apps échouent au pull de l'image.
  • [ ] L'organisation npm @matvi-consulting existe.
  • [ ] L'environnement GitHub release existe (Settings → Environments). Règles conseillées : approbation requise, déploiement limité aux tags v*.
  • [ ] Le package npm a un Trusted Publisher GitHub Actions : MATVI-CONSULTING/monitoring-agent-cloud, workflow release.yml, environnement release, « Allow npm publish » coché. Aucun token npm n'est nécessaire.