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

codiedev

v0.7.10

Published

Connect Claude Code, Codex, Cursor, or VS Code Copilot to CodieDev for org-wide session capture and artifact collaboration

Readme

codiedev

Connect Claude Code or Codex to CodieDev for org-wide session capture.

Usage

npx codiedev connect

The CLI will prompt you for an API token (get one at https://codiedev.com/portal/integrations/claude-code), then install a capture hook into whichever agent CLIs are present on your machine:

  • Claude CodeSessionEnd hook in ~/.claude/settings.json
  • CodexStop hook in ~/.codex/hooks.json

If both are installed, hooks are wired up for both. If neither is installed, the config is saved and you can re-run connect after installing one.

What gets captured

  • Only sessions inside repos your workspace already tracks
  • Transcript + basic stats (message count, tool calls)
  • Processed into summaries and embeddings server-side for search in /portal/memories

Each captured memory records its source (claude-code or codex) so you can filter in the portal.

Codex note

Codex doesn't currently expose a SessionEnd event, so the hook runs on Stop (fires after each assistant turn). The backend dedupes by (company, session_id) and replaces the stored transcript on re-upload so the latest turn's snapshot wins. Summarization happens once per session; subsequent turn uploads keep the raw transcript fresh but don't re-summarize (to avoid running up LLM cost).

Config

Written to ~/.codiedev/config.json. Override the backend with CODIEDEV_URL if needed.