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

@thunkedai/cli

v0.1.1

Published

Capture anything to your AI-powered second brain from the terminal

Downloads

0

Readme

@thunkedai/cli

Capture anything to your Thunked second brain from the terminal.

Install

npm install -g @thunkedai/cli

The published package is @thunkedai/cli; the executable command is thunked.

For local development from this repo:

cd cli
npm install
npm run build
npm link

For agent/MCP integrations, the currently published MCP package remains:

npx thunked-mcp

Setup

Interactive local setup:

thunked login

Grab your user-owned API key from the developer settings in the Thunked app and paste it when prompted.

Script/CI/agent setup:

export THUNKED_API_KEY="thunked_..."

THUNKED_API_KEY is always preferred over the local config file and is never written to disk by the CLI. In v1, API keys are user-owned; team captures are authorized through the key owner's team membership.

Usage

# Capture a URL
thunked capture https://example.com/interesting-article

# Capture a quick note
thunked capture --text "Remember: the answer is 42"

# Capture into a team inbox or shared collection you can write to
thunked capture https://example.com --team acme
thunked capture --text "Team note" --team acme/research

# Search your brain
thunked search "machine learning"

# See recent items
thunked recent

# Check account status
thunked status

# Check local config, auth presence, and API reachability
thunked doctor

JSON output

Read commands support --json for scripting:

thunked search "rust" --json | jq '.data[0].url'

Custom API endpoint

thunked config baseUrl http://localhost:3000

Auth source inspection

thunked config

This prints whether auth is coming from THUNKED_API_KEY or the local config file without revealing the key.

Diagnostics

thunked doctor
thunked doctor --json
thunked doctor --no-probe

doctor checks the CLI version, Node.js version, API base URL, auth source, and API reachability. It reports whether an API key is present and valid without printing the key or account details.

Development

git clone https://github.com/shugart/jons-brain
cd jons-brain/cli
npm install
npm test
npm run build
node dist/index.js --help
npm pack --dry-run