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

claudesidian

v1.1.1

Published

Bridge Claude Code conversations to your Obsidian vault with /send-to-vault

Readme

🤖 claudesidian

Claude Code × Obsidian, automated. Save any Claude response to your vault with a single command — no copy-paste, no faff, just vibes.


✨ What is this?

You're mid-conversation with Claude, it just dropped an absolute banger of an explanation, and you think "I want that in my Obsidian vault forever."

Normally you'd copy it, switch apps, create a note, paste it, add a title, sort the formatting... ugh.

With claudesidian, you just type /send-to-vault. That's it. Claude writes the note, dates it, adds frontmatter, and drops it straight into your vault. Obsidian picks it up instantly. You stay in flow. 🌊


🚀 Install

npx claudesidian

You'll get a beautiful interactive setup that:

  • 📋 Explains exactly what it's going to do before doing anything
  • 📍 Shows you the locations it'll write to
  • 🔐 Lists the permissions it'll add to Claude Code
  • Asks for confirmation before touching a single file

🎮 Usage

In any Claude Code conversation, just type:

/send-to-vault

Claude will:

  1. 🔍 Grab the last response from the conversation
  2. 📅 Generate a dated filename — e.g. 2026-02-27 React Query Setup Guide.md
  3. 📝 Wrap it in YAML frontmatter (created, source: claude)
  4. 💾 Write it straight to your vault folder

Obsidian detects the new file immediately. No plugin needed. Pure filesystem magic. 🪄


⚙️ Configuration

Config lives at ~/.claude/vault-config.json:

{
  "vault_path": "~/Documents/MyVault",
  "folder": "🤖 Inbox"
}

To reconfigure (e.g. new vault, different folder), just run npx claudesidian again — it'll show your current settings and let you update them.


🔐 Permissions

claudesidian automatically configures the right Claude Code permissions in ~/.claude/settings.json so you're never interrupted mid-save with an approval prompt:

| Permission | What it allows | |---|---| | Write(~/your-vault/**) | Creating new notes | | Edit(~/your-vault/**) | Updating existing notes | | Bash(mkdir -p ~/your-vault/*) | Creating folders (scoped to your vault) | | Read(~/.claude/vault-config.json) | Reading your config |

These are scoped to your vault path — nothing broader than it needs to be.


📦 Requirements


📄 License

MIT — go wild. 🎉