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

nostr-tribes

v0.3.2

Published

Client library for using nostr tribes

Readme

Nostr Tribes

Typescript library to work with Nostr tribes in the browser and in nodejs.

Learn more about tribes at https://tribewiki.org/Tribe or browse tribes at https://nostribe.org

Usage

Basic usage:

let tribe = new Tribe("32149:leader-pubkey:tribeid"", {relays}) // or new Tribe("naddr1...")
await tribe.sync()  // Fetch members
await tribe.sync_profiles() // Fetch member profiles (name, avatar, nip05)
tribe.subscribe() // Subscribe for changes in tribe membership

tribe.member(pubkey) // returns true if pubkey is a member
tribe.entry(pubkey)  // returns all known info on member (name, nip05, avatar, parent)

some_events = ... // Fetch nostr events from a relay

let judgements = await tribe.judgeEvents(some_events)  // Decide which events are approved by the tribe
// Returns {[event_id]: [verdict, object, stamp]}
// verdict is either 'curate', 'neutral' or 'ban'
// object is either 'pubkey' or 'event'
// if object is 'event', the corresponding kind:78 stamp is returned as the 3rd item in the list

await tribe.stamp_event(some_event)  // Curate an event (stamp it) and upload the stamp to tribe relays.
await tribe.stamp_pubkey(some_event.pubkey)  // Add a new member to the tribe, store stamp on tribe relays.

Roadmap

  • Ban should have effect only on parent's sub-tree
  • Maintain parents[] instead of a single parent for each member
  • Pass log_fn in constructor for logging. If not passed, do not log.
  • Add a way to maintain permissions for members. These perms can be queried by clients, or have effect on core mechanics of tribes. E.g. moderator perm.
  • Invitations (possibly through an online bot that keeps invite tree private)