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

reads-ts

v0.3.14

Published

Reads is a local-first research tracking and memory CLI. It helps humans and agents turn questions into hypotheses, evidence, and explicit graph links, while keeping every change auditable through an event log.

Downloads

106

Readme

Reads

Reads is a local-first research tracking and memory CLI. It helps humans and agents turn questions into hypotheses, evidence, and explicit graph links, while keeping every change auditable through an event log.

Why Reads

  • Keep research state consistent across sessions and agents.
  • Preserve provenance and deterministic history for every write.
  • Move from ad-hoc notes to explicit reads, edges, tasks, and lifecycle transitions.

For the deeper rationale, read docs/philosophy-of-reads.md.

Installation

Requirements:

  • Node.js 20+ (recommended for npm/global install)
  • Bun 1.3+ (required for source-mode development commands)
  • jq (optional, for JSON scripting examples)

Install from source:

git clone <your-fork-or-this-repo-url> reads-ts
cd reads-ts
bun install

Run from source:

bun run src/cli.ts --help

Supported global install flow:

cd reads-ts
bun link
export BUN_INSTALL="${BUN_INSTALL:-$HOME/.bun}"
export PATH="$BUN_INSTALL/bin:$PATH"
rd --help

Install from npm:

npm install -g reads-ts
rd --help

Runtime note:

  • Published CLI uses Node (dist/cli.js with #!/usr/bin/env node).
  • Bun is still the repository package-manager/development standard.

Platform support:

  • Linux and macOS are the primary validated targets.
  • Windows is currently best-effort (no dedicated CI matrix yet).

Persist PATH for future bash shells:

echo 'export BUN_INSTALL="$HOME/.bun"' >> ~/.bashrc
echo 'export PATH="$BUN_INSTALL/bin:$PATH"' >> ~/.bashrc

Quick start

RD="bun run src/cli.ts"
W1=$(mktemp -d)
W2=$(mktemp -d)

$RD --workspace "$W1" init --prefix rd
R1=$($RD --workspace "$W1" --json create "Claim: Tau217 predicts progression" --type claim | jq -r '.data.readId')
R2=$($RD --workspace "$W1" --json create "Finding: cohort result supports Tau217" --type finding | jq -r '.data.readId')
$RD --workspace "$W1" link "$R2" "$R1" --type supports --justification "Cohort analysis supports the claim"
$RD --workspace "$W1" transition "$R1" under-review --evidence "Initial supporting evidence logged"
$RD --workspace "$W1" task create "$R1" --type research --instruction "Find two independent replications"
$RD --workspace "$W1" doctor
$RD --workspace "$W1" export "$W1/snapshot.json"
$RD --workspace "$W2" import "$W1/snapshot.json"

Documentation

  • Docs home: docs/README.md
  • Docs landing page (GitHub Pages): docs/index.md
  • Tutorial and quickstart: docs/tutorial-quickstart.md
  • Philosophy of Reads: docs/philosophy-of-reads.md
  • CLI reference: docs/cli.md
  • Operations and recovery: docs/operations.md
  • Architecture and data model: docs/architecture.md
  • Agent prompt JSON contract: docs/agent-prompt-json.md
  • Releasing and npm publishing: docs/releasing.md

Development policy

For contributors, dependency management is Bun-only:

  • bun.lock is the only lockfile.
  • package.json declares packageManager: bun@....
  • Run bun run check:policy in local checks and CI.