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

libra-logs

v0.1.1

Published

One command to wire your codebase into Libra Logs: npx libra-logs

Readme

libra-logs

Set up Libra Logs in your project with one command:

npx libra-logs

The installer detects your stack (Node servers, Next.js, Python FastAPI, Go net/http), reuses your existing OpenTelemetry setup if you have one, ships logs to Libra Logs alongside wherever they go today, adds deploy context and trace ids to every line, and confirms your first log live. All edits land on a new git branch; nothing is committed or pushed without your yes.

Source files are only sent to a model after you approve it (or pass --ai-consent). .env* files and secrets are never sent.

Other commands:

npx libra-logs audit                     # check an existing integration for gaps
npx libra-logs deploy --service api      # report a deploy (run in CI after deploying)
npx libra-logs mcp add                   # connect Claude Code / Cursor to Libra Logs
npx libra-logs fix-blind-spots <change>  # add logs to changed code that emits none