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

@neelegirly/libsignal

v1.0.28

Published

Signal protocol crypto dependency for @neelegirly/baileys on Node.js

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

neelegirlyneelegirly

Keywords

signalwhispersystemscryptosignal-protocolneelegirlybaileys

Readme

🔐 @neelegirly/libsignal 🔐

Crypto Core fuer den Neelegirly Stack

Signal Sessions · Key Material · E2E Foundation

npm baileys wa-api

🗝️ Release-Stack: @neelegirly/libsignal 1.0.28 · @neelegirly/baileys 2.2.17 · @neelegirly/wa-api 1.7.16

@neelegirly/libsignal ist die kryptografische Signal-Abhaengigkeit fuer @neelegirly/baileys und damit indirekt auch fuer @neelegirly/wa-api. Das Paket liefert den E2E-Kern fuer Session-Aufbau, Key-Verarbeitung und sichere Nachrichtenfluesse.

✨ Highlights

| Bereich | Beschreibung | Status | | --- | --- | --- | | 🔑 Key Material | zentrale Primitive fuer Session-/Schluessel-Operationen | ✅ | | 🛡️ E2E Core | Basis fuer verschluesselte Nachrichten im Neelegirly-Stack | ✅ | | 🧩 Stack-Kompatibel | sauberer Fit fuer baileys und wa-api | ✅ | | 🎀 Klarer Scope | @neelegirly/libsignal als eindeutige Release-Basis | ✅ |

📦 Kompatibilitaet

  • @neelegirly/libsignal: 1.0.28
  • @neelegirly/baileys: 2.2.17
  • @neelegirly/wa-api: 1.7.16

🚀 Installation

npm install @neelegirly/[email protected] --save-exact

⚡ Minimalbeispiel

const libsignal = require('@neelegirly/libsignal')

console.log('libsignal geladen:', typeof libsignal === 'object')

🩷 Scope und Rolle im Stack

  • @neelegirly/libsignal = Crypto-Core
  • @neelegirly/baileys = WhatsApp-Web-Layer
  • @neelegirly/wa-api = Multi-Session-Wrapper

Damit bleibt der Aufbau im gesamten Neelegirly-Stack klar und release-sicher.

🔄 Release-Notizen

  • README neu im Glow-up-Stil aufgebaut
  • Stack-Versionen auf 1.0.28 / 2.2.17 / 1.7.16 angehoben
  • weiterhin fokussiert auf den stabilen Crypto-Einsatz ohne Bot-Wrapper-Ballast