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

@listen-fire/attio

v0.12.7

Published

Attio (objects, records, lists, notes, tasks, comments, files) as a module: read, written, and signed webhooks. Loaded in process by the platform, served by serve-module everywhere else.

Readme

@lf/attio

Attio as a module: records, lists, files and webhooks. A connection uses one of two credentials, and listen-fire credential add asks for the name of the one you want.

Connect with an access token

The simplest way in, and the one for a service account. Create a token in Attio (Workspace settings, Developers, Access tokens) with read-write access to records and webhooks, then:

listen-fire connect @lf/attio                       # answers the OAuth app questions; leave them empty if you only use tokens
listen-fire credential add --module attio henry_attio --credential attio_token
#   Access token: <the token>      Base URL: <enter, unless you proxy Attio>

The credential attio_token holds accessToken and an optional baseUrl. The token is entered once and never refreshed.

Connect with OAuth

For a user who signs in through Attio's authorize page, with your own OAuth app (client id and secret, the redirect URI listen-fire connect prints):

listen-fire connect @lf/attio
listen-fire credential add --module attio henry_attio --credential attio

Either way the movement says connect attio using henry_attio; Attio receives the same bearer header from both.