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

@dreamteamer/recordings

v0.1.1

Published

Meeting recordings for a dreamteamer workspace — imported by content hash, matched to their meeting, and transcribed offline in Hebrew and English.

Readme

@dreamteamer/recordings

Audio recordings of your meetings, each matched to its meeting and transcribed on your own machine: Hebrew and English, speakers told apart.

npm install @dreamteamer/recordings @dreamteamer/meetings @dreamteamer/contacts @dreamteamer/companies @dreamteamer/users @dreamteamer/assets
npx dreamteamer compile

the flow

  1. Drop audio into <an INBOX_FOLDERS root>/meeting-recordings/, named [date] [who] where you can (2026 08 30 1500 Northwind weekly.m4a, Dana Oren jul22.m4a; a Hebrew month name works too).
  2. /fetch-new-recordings — dedupes by content hash, archives each new file under ${env:FILES_FOLDER}/meeting-recordings/, moves the original to the inbox root's trash/, and creates a meeting-recordings record.
  3. /match-recording-to-meeting — links each recording to its meeting.
  4. /transcribe-recording — writes the transcript into the recording record.

A file handed straight to a session, or a pasted transcript, skips the inbox: the transcribing-recordings skill covers both.

| alone | with others | |---|---| | recordings pulled from an inbox by content hash, matched to their meeting, transcribed; each meeting's recordings list generated from the recordings that point at it | meeting-docs reads the transcript: summarise, extract tasks, critique |

| needs | for | |---|---| | @dreamteamer/meetings (and what it needs) | the meeting a recording belongs to | | INBOX_FOLDERS and FILES_FOLDER, declared in your workspace's dreamteamer.vars | where recordings arrive (a newline-separated list of roots) and where they are archived (a local folder) | | ffmpeg, ffprobe, uv and about 1.6 GB of models, downloaded once | transcribing audio; a pasted transcript needs only uv | | TRANSCRIBING_MODELS_DIR, an absolute path exported in the environment that runs the transcriber | where the models live; without it they sit inside the skill folder, which compile and npm ci regenerate |