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

@xnetjs/slack-compat

v0.0.2

Published

Slack wire-protocol compatibility primitives — Block Kit + mrkdwn → GitHub-flavored markdown, incoming-webhook + slash-command parsing, and signing-secret verification. Pure logic, zero runtime dependencies (node:crypto only). The shared core under XNet's

Downloads

298

Vulnerabilities

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

Links

Git

Maintainers

csmotherscsmothers

Keywords

Readme

@xnetjs/slack-compat

Slack wire-protocol compatibility primitives for XNet — the shared, pure-logic core that lets integrations written against Slack work against XNet (exploration 0198).

Zero runtime dependencies (node:crypto only). Used by the Slack migration connector (@xnetjs/plugins) and the hub slack-compat feature (@xnetjs/hub).

What's here

| Export | Purpose | | --- | --- | | slackMrkdwnToMarkdown(text) | Translate Slack mrkdwn (<url\|label>, <@U1>, *bold*, escaped entities) → GitHub-flavored markdown. | | blockKitToMarkdown(blocks) | Best-effort Block Kit (header/section/context/divider) → markdown. Interactive blocks degrade to their text. | | normalizeIncomingWebhook(payload) | Collapse a Slack incoming-webhook body (blocks → attachments → text) into a transport-agnostic { content, channelHint?, username?, iconEmoji? }. | | parseSlashCommand(body) / formatSlashResponse(opts) | Slack-compatible slash-command request parsing + response formatting (defaults to ephemeral, matching Slack). | | verifySlackSignature(opts) / signSlackRequest(opts) | v0=HMAC_SHA256 signing-secret verification with replay protection. |

Design notes

  • Lossy by design. ChatMessage.content is GFM markdown; Slack messages are Block Kit JSON / legacy attachments. Translation is best-effort — buttons, selects, modals and App Home have no markdown equivalent and degrade to their text. Callers can park the original JSON in an ext: overlay for richer rendering later.
  • Pure + injectable. No I/O, no globals, no clock except an injectable nowSeconds on signature verification — so every branch is unit-testable.

See the exploration for the full tiered-compatibility plan and what is deliberately deferred (OAuth authorization server, bot identity, the full Events API, interactive Block Kit).