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

@onenomad/przm-cortex-adapter-loom

v0.7.0

Published

Loom recordings + transcripts source adapter for Cortex.

Readme

@onenomad/cortex-adapter-loom

Loom recordings + transcripts source adapter.

Note on Loom API access. Loom's workspace/REST API requires a Business or Enterprise plan, and the exact endpoint shapes are evolving. This adapter is structured so its HTTP client is the only surface that depends on Loom's specifics — swap it when Loom's API changes without touching the adapter/transform layer.

Config in config/cortex.yaml:

adapters:
  loom:
    package: "@onenomad/cortex-adapter-loom"
    enabled: true
    schedule: "*/15 * * * *"
    config:
      workspace: "yourcompany"             # Loom workspace slug
      folders: []                          # folder ids to scope, empty = all
      pageSize: 50
      maxRecordingsPerRun: 0               # 0 = unlimited
      folderToProject:                     # rule-based classifier
        fld_abc: engineering
      defaultProject: ""
      skipWithoutTranscript: true          # ignore recordings w/o transcript

Required secrets (.env):

  • LOOM_API_KEY — workspace API key from Loom admin

Feeds into @onenomad/cortex-pipeline-meeting (the 3-pass extraction). Each recording's transcript becomes a meeting-shaped ClassifiedItem whose run through the pipeline produces a brief plus per-decision and per-action-item memories.