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

@aaaaorg/logslim

v0.1.0

Published

Extract signal from LLM session transcripts — decisions, errors, commands, files changed

Readme

logslim

Extract signal from LLM session transcripts — decisions, errors, commands, files changed.

Turn 10MB session logs into 10KB summaries. Zero dependencies.

Install

npm install -g @aaaaorg/logslim

Usage

# Summarize a session (markdown output)
logslim session.jsonl

# Quick stats
logslim session.jsonl --stats
# be716422...  160 msgs  162 tools  10m  0 decisions  0 errors  32 files

# JSON output
logslim session.jsonl --json

# Plain text
logslim session.jsonl --format text

# Pipe from stdin
cat session.jsonl | logslim --stdin

# Multiple files
logslim *.jsonl --stats

# Strip tool call analysis
logslim session.jsonl --no-tools

# Unlimited content per message (default: 500 chars)
logslim session.jsonl --max-content 0

What it extracts

  • Decisions — "chose to", "decided", "going with", "skipping"
  • Errors — error messages from tool outputs
  • Files touched — read/write/edit operations + paths in output
  • Commands run — shell commands executed via exec tools
  • Key exchanges — trimmed user/assistant conversation (first 3 + last 2)
  • Stats — message count, tool calls, duration, model used

Output formats

Markdown (default)

# Session: be716422-...
**Started:** 2026-02-14 01:00 | **Duration:** 10m | **Messages:** 160 | **Tool calls:** 162

## Decisions
- Skipping codebase mapping...

## Errors
- Error: ENOENT no such file...

## Files Touched
- /path/to/file.js

Stats (one-liner per file)

be716422...  160 msgs  162 tools  10m  0 decisions  0 errors  32 files

JSON

Full structured object with all extracted data.

Input format

Reads JSONL files as produced by OpenClaw / Claude session logs. Each line is a JSON object with type, timestamp, and message fields.

Why

LLM session transcripts are huge (multi-MB) and mostly noise — tool call payloads, base64 images, repeated context. logslim extracts the 1% that matters: what was decided, what broke, what files changed.

Use cases:

  • Knowledge extraction — feed summaries into memory systems instead of raw transcripts
  • Cost auditing — quick stats across hundreds of sessions
  • Debugging — find errors without reading 10MB of logs
  • Archiving — keep summaries, delete raw logs

License

MIT