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

@boxingoctopus/n8n-nodes-bluesky

v1.3.1

Published

n8n community node for posting to Bluesky (ATProto)

Readme

n8n-nodes-bluesky

n8n community node for posting to Bluesky (ATProto).

Features

  • Post to Bluesky with text
  • Automatic link and mention parsing - Links and @mentions are automatically detected and parsed using ATProto's RichText API
  • Upload images (up to 4 per post)
  • Reply to posts
  • Manual rich text facets (optional, overrides auto-parsing)
  • Credential testing to verify connection

Installation

npm install n8n-nodes-bluesky

Credentials

  1. Go to https://bsky.app/settings/app-passwords
  2. Create a new app password
  3. Use your Bluesky handle (e.g., username.bsky.social) and the app password in the credentials

Usage

  1. Add the Bluesky node to your workflow
  2. Configure credentials with your handle and app password
  3. Enter the text you want to post
  4. Links and mentions (@username) are automatically detected and parsed
  5. Optionally:
    • Add images (comma-separated binary property names)
    • Add reply URI to reply to a post
    • Provide manual facets (overrides auto-parsing)
    • Disable auto-parsing if you want plain text only

Development

GitHub Actions

This repository includes GitHub Actions for:

  • Automated npm publishing: Publishes to npm when version changes
  • Integration tests: Runs tests against the Bluesky API

Setup for npm Publishing

To enable automated publishing, you need to create an npm Automation Token (not a regular token):

  1. Go to https://www.npmjs.com/settings/YOUR_USERNAME/tokens
  2. Click "Generate New Token"
  3. Select "Automation" token type (this type doesn't require 2FA/OTP)
  4. Copy the token
  5. Add it as a GitHub secret named NPM_TOKEN in your repository settings

Important: Use an Automation token, not a regular token. Automation tokens don't require 2FA/OTP codes, making them perfect for CI/CD.

Development

GitHub Actions

This repository includes GitHub Actions for:

  • Automated npm publishing: Publishes to npm when version changes
  • Integration tests: Runs tests against the Bluesky API

Setup for npm Publishing

To enable automated publishing, you need to create an npm Automation Token (not a regular token):

  1. Go to https://www.npmjs.com/settings/YOUR_USERNAME/tokens
  2. Click "Generate New Token"
  3. Select "Automation" token type (this type doesn't require 2FA/OTP)
  4. Copy the token
  5. Add it as a GitHub secret named NPM_TOKEN in your repository settings

Important: Use an Automation token, not a regular token. Automation tokens don't require 2FA/OTP codes, making them perfect for CI/CD.

License

MIT