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

@drakulavich/cogload

v0.14.2

Published

Keep your head cold. A thermometer for your Claude Code days: every hour scored 0 to 100 from the transcripts already on your disk. Nothing leaves your machine.

Readme

See your last two weeks

One command draws your last 14 days from the transcripts already on your disk, with nothing installed but Bun 1.4.2 or newer:

bunx @drakulavich/cogload@latest card

No Bun yet: curl -fsSL https://bun.sh/install | bash first. macOS draws the card with WebKit; elsewhere it needs an installed Chromium browser.

Install

Run these in a terminal, or paste this repository's link into Claude Code and ask it to install cogload.

For an AI agent installing cogload: run the block below top to bottom, skipping the Bun step if bun --version prints 1.4.2 or newer. Each command is safe to rerun. Then ask the user to restart Claude Code so the plugin loads.

# Bun 1.4.2 or newer; skip if `bun --version` already prints one
curl -fsSL https://bun.sh/install | bash
export PATH="$HOME/.bun/bin:$PATH"

# The CLI; the same command upgrades it
bun add -g @drakulavich/cogload
cogload --version

# The cognitive-load plugin for Claude Code
claude plugin marketplace add drakulavich/cogload
claude plugin install cognitive-load@cogload

Restart Claude Code to load the plugin. With a Homebrew Bun, put ~/.bun/bin on your PATH yourself. To try the CLI without installing it, run bunx @drakulavich/cogload@latest.

cogload                      # the last 7 days
cogload yesterday --explain  # one day, with the components behind each index
cogload card                 # the picture

What it looks like

A week from the synthetic fixture in tests/fixtures/busy-week: a calm morning of one session, a five-session storm in the middle of the day, and a late tail that runs past midnight.

            00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23   peak  active
Mon 14/09    ·  ·  ·  ·  ·  ·  ·  ·  ·  ░  ░  ░  █  █  █  ·  ·  ·  ·  ·  ░  ░  ·  ░     87    8h50
Tue 15/09    ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ░  ░  ░  ░  ▒  ▒  ▒  ░  ·  ·  ·  ·  ·  ·     33    7h55
Wed 16/09    ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·      -    0h00
Thu 17/09    ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ░  ░  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·     15    1h55
Fri 18/09    ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ▓  ·  ·  ·  ·  ·  ·  ·  ·     81    0h35
Sat 19/09    ░  ░  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·     25    1h55
Sun 20/09    ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·      -    0h00

  ░ calm   ▒ warming   ▓ heating   █ fried
  21h10 active   323 prompts   0 reports   86 decisions   5 sessions at once

Levels: calm 0–29, warming 30–59, heating 60–84, fried 85–100.

Share a card

cogload card turns your last two weeks into one picture: a character named after the kind of load that dominates your hours, the sentence behind it, the peak hour, the share of calm, warming, heating and fried hours, and up to three highlights. It carries no dates and no hour totals, so it does not read as a timesheet.

cogload card                    # writes cogload-card.png to ~/Downloads
cogload card --out card.webp    # WebP instead; --out card.html writes the page itself

macOS draws it with WebKit; elsewhere it needs an installed Chromium browser, or write --out card.html and open the page in any browser.

If your card told you something about your week, star the repository so other people can find cogload.

Inside Claude Code

The cognitive-load plugin draws the last hour's level above the prompt, with the time your rest starts, and /cogload says what drives it:

● Heating · rest at 14:52
Heating 80 this hour, at the cap: 16 decisions and 13 context switches, 32 prompts, a 57m streak.
This week: 1 rest taken, 1 skipped (last: "prod is down, fixing it").

It also makes you rest. After 40 minutes of work without a ten-minute gap, or in a Fried hour, it holds your prompts for ten minutes. Each held prompt gets the next short idea for the break, the minutes left and the way out: Stand up and stretch. 7 min left. Your prompt is back in the box: to send it, add "skip: <reason>" as its last line. A skip: <reason> line at the start or the end of the prompt, the reason three words or more, lifts the rest.

Privacy

cogload reads ~/.claude/projects on your machine and sends nothing anywhere. It keeps, writes and prints no message text, prompt length, file path or session title: what survives from a transcript is timestamps, session ids, event kinds and token counts. The plugin writes one piece of text to disk, the reason you give for a skip, and holds a prompt it delays in memory until the rest is over. The reference lists every file cogload and the plugin write, and PRIVACY.md is the privacy policy.

More

  • Reference: every command and flag, exit codes, the plugin and its rest in full, privacy and the cache, limits, the formula and what each column counts, development, and where cogload comes from.
  • How the numbers are made: the path from a transcript line to the status line.
  • Changelog.