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

@astratra/tooling

v1.0.1

Published

Generic audit, test, and deploy tooling for Astratra workspaces.

Readme

@astratra/tooling

CLI pour l'audit et les tâches génériques de maintenance de projet. Fournit un binaire astratra. Dépend de @astratra/core.

Rien dans ce package ne connaît la structure de dossiers, les noms de rôles ou la cible de déploiement d'un projet précis — chaque chemin et pattern a une valeur par défaut neutre, surchargeable via astratra.config.json (ou .js) à la racine du projet consommateur.

Commandes

astratra audit:secrets [--dir=<path>]   # détecte les secrets littéraux loggés ou renvoyés dans des réponses API
astratra audit:routes  [--dir=<path>]   # détecte les routes Express *.routes.js sans middleware d'auth apparent
astratra audit:i18n    [--dir=<path>]   # détecte les incohérences de clés de traduction entre langues
astratra test                           # lance le script 'test' de chaque workspace et agrège le résultat
astratra deploy [--mode=<name>]         # exécute les étapes de déploiement définies dans votre propre config — aucune logique de déploiement intégrée

Chaque commande retourne un exit code non-zéro en cas de findings/échecs — utilisable directement en CI.

Configuration (astratra.config.json)

{
  "audit": {
    "secrets": { "dirs": ["src"] },
    "routes": {
      "dirs": ["src"],
      "authMiddlewarePatterns": ["authMiddleware", "authorizeRoles"],
      "publicMarkers": ["public", "webhook", "health"]
    },
    "i18n": { "localesDir": "locales", "sourceDirs": ["src"] }
  },
  "test": { "workspaces": null },
  "deploy": {
    "steps": ["npm run build", "npm test"],
    "modes": { "fast": { "skip": ["step-2"] } }
  }
}

deploy est un orchestrateur, pas un mécanisme de déploiement : il exécute simplement les commandes shell que vous listez, dans l'ordre, et s'arrête au premier échec. Il ne connaît ni pm2, ni Docker, ni aucun VPS précis — cette logique reste dans votre propre projet.

Tests

npm test --workspace @astratra/tooling