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

@kakedashi/paylog

v0.3.0

Published

CLI tool to view your MPP spending history powered by paylog.dev

Readme

paylog

CLI tool to view your MPP and x402 spending history, powered by paylog.dev.

Usage

npx @kakedashi/paylog report --days 7
npx @kakedashi/paylog report --days 30 --enrich
npx @kakedashi/paylog report --chain base
npx @kakedashi/paylog report --chain all
npx @kakedashi/paylog wallet
npx @kakedashi/paylog balance

Commands

paylog report

Show a spending report for your wallet.

Options:
  -d, --days <n>          Past N days (default: 7)
  --from <date>           Start date YYYY-MM-DD
  --to <date>             End date YYYY-MM-DD
  --wallet <address>      Override auto-detected wallet
  --chain <chain>         Chain: tempo (default), base, or all
  --private-key <key>     EVM private key for x402 payment (base/all)
  --enrich                Enrich Locus payments using local history (tempo only)

--chain values

| Value | Protocol | Endpoint | Cost | |---|---|---|---| | tempo (default) | MPP | /api/v1/report | $0.001 USDC / Tempo | | base | x402 | /api/v1/x402/report?chain=base | $0.01 USDC / Base | | all | x402 | /api/v1/x402/report?chain=all | $0.01 USDC / Base |

--chain all combines MPP (Tempo) + x402 (Base) into a single report.

x402 payment (--chain base or --chain all)

x402 payment requires an EVM private key on Base mainnet:

# via environment variable
EVM_PRIVATE_KEY=0x... npx @kakedashi/paylog report --chain base

# via option
npx @kakedashi/paylog report --chain base --private-key 0x...

The wallet address is derived automatically from the private key. Use --wallet 0x... to query a different address while signing with your key.

The --enrich flag reads your shell history and Claude Code chat logs to identify which Locus MPP services you used, since all Locus services share a single on-chain recipient address.

paylog wallet

Display the auto-detected wallet address and its source.

paylog balance

Run tempo wallet whoami (requires the Tempo CLI).

Wallet Auto-Detection

For Tempo (MPP) reports, the wallet address is resolved in this order:

  1. ~/.tempo/wallet/keys.tomlwallet_address field
  2. ~/.agentcash/wallet.jsonaddress field
  3. ~/.mppx/wallet.jsonaddress field
  4. --wallet 0x... option

For x402 (Base) reports, the wallet is derived from EVM_PRIVATE_KEY or --private-key.

--enrich Details

Locus routes 40+ services through a single on-chain recipient (0x060b0fb0...), making them indistinguishable from on-chain data alone. The --enrich flag uses local history to estimate which service was used:

History sources scanned:

  • ~/.zsh_history (with timestamps)
  • ~/.bash_history
  • ~/.local/share/fish/fish_history
  • ~/.claude/projects/*/chat.jsonl

Matching logic:

| Confidence | Condition | |---|---| | High | Timestamp matches within ±30 seconds | | Medium | Timestamp matches within ±60 seconds + price match | | Low | Price match only |

Example output:

  Locus (paywithlocus.com)    $0.048   4 txns
      ┌─ Estimated breakdown (from local history) ──────────
      │ ✓ Brave Search      $0.010  1 txn   confidence: high
      │ ✓ Perplexity        $0.010  1 txn   confidence: high
      │ ? DeepSeek          $0.020  1 txn   confidence: medium
      └─ * estimated via local history correlation ─────────

Cost

| Chain | Cost | |---|---| | Tempo (MPP) | $0.001 USDC per call | | Base (x402) | $0.01 USDC per call |

License

MIT