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

@anura-gate/watcher-slack

v0.3.0

Published

GATE Watcher — Self-hosted Slack Bot. Tokens never leave your machine.

Readme

GATE Watcher — Slack

Self-hosted daemon that connects your Slack Bot to GATE cloud for security processing via Socket Mode. Your bot tokens never leave your machine.

How it works

Your Machine (Watcher)              GATE Cloud
┌─────────────────────┐        ┌──────────────────┐
│ Slack Socket Mode   │───────>│ Security pipeline │
│ (tokens stay HERE)  │<───────│ (redact, policy,  │
│                     │ poll   │  audit, forward)  │
└─────────────────────┘        └──────────────────┘

Quick Start (CLI)

cd gate-watcher-slack
npm install

# Create .env (or pass env vars directly)
cp .env.example .env
# Fill in GATE_KEY, GATE_INTEGRATION_ID, SLACK_BOT_TOKEN, SLACK_APP_TOKEN

npm start

Embed in Your App (SDK)

npm install @anura-gate/watcher-slack
const { GateSlackWatcher } = require("@anura-gate/watcher-slack");

const watcher = new GateSlackWatcher({
  gateKey: "gk-xxx",
  integrationId: "int_xxx",
  botToken: "xoxb-xxx",
  appToken: "xapp-xxx",
});

watcher.on("ready", (botUserId, botName, teamName) => {
  console.log(`Slack connected: ${botName} in ${teamName}`);
});

// Every message after GATE security processing
watcher.on("message", (event, result) => {
  console.log(`From: ${event.user}, Text: ${event.text}`);
  console.log(`Security actions: ${result.securityActions}`);
  console.log(`Blocked: ${result.blocked}`);
});

watcher.on("reaction", (event, result) => {
  console.log(`Reaction: ${event.reaction} by ${event.user}`);
});

watcher.on("action_result", ({ action, success, error }) => {
  console.log(`${action}: ${success ? "done" : error}`);
});

await watcher.start();

// Later...
await watcher.stop();

SDK Events

| Event | Args | Description | |---|---|---| | ready | (botUserId, botName, teamName, teamId) | Connected to Slack | | message | (event, result) | Message received and processed by GATE | | reaction | (event, result) | Reaction added, processed by GATE | | member_joined | (event, result) | Member joined a channel | | mention | (event, result) | Bot mentioned in a channel | | action | (action) | Outbound action received from GATE queue | | action_result | ({ actionId, action, success, result, error }) | Outbound action completed | | gate_error | ({ path, status, error }) | GATE API call failed | | limit_reached | (type) | Plan limit hit | | disconnected | (reason) | Disconnected from Slack | | stopped | — | Watcher fully shut down |

SDK Options

| Option | Required | Default | Description | |---|---|---|---| | gateKey | Yes | — | Virtual key (gk-xxx) | | integrationId | Yes | — | Integration ID (int_xxx) | | botToken | Yes | — | Slack Bot User OAuth Token (xoxb-...) | | appToken | Yes | — | Slack App-Level Token for Socket Mode (xapp-...) | | gateUrl | No | "https://anuragate.com" | GATE cloud URL | | heartbeatInterval | No | 30000 | ms between heartbeats | | pollInterval | No | 3000 | ms between outbound polls | | sessionId | No | — | Session ID for multi-tenant use | | sessionLabel | No | — | Human-readable session label | | sessionMetadata | No | {} | Arbitrary metadata for the session |

Setup

  1. Go to api.slack.com/apps and create a new app
  2. Under Socket Mode, enable Socket Mode and generate an App-Level Token with connections:write scope — this is your SLACK_APP_TOKEN (xapp-...)
  3. Under OAuth & Permissions, add Bot Token Scopes: chat:write, reactions:write, channels:history, groups:history, im:history
  4. Install the app to your workspace and copy the Bot User OAuth Token — this is your SLACK_BOT_TOKEN (xoxb-...)
  5. Under Event Subscriptions, enable events and subscribe to: message.channels, message.groups, message.im, reaction_added, member_joined_channel, app_mention
  6. Go to GATE Dashboard → Integrations → Add Integration, select Slack, copy the Integration ID
  7. Copy your Virtual Key from the Keys page

Environment Variables

| Variable | Required | Description | |---|---|---| | GATE_KEY | Yes | Your GATE virtual key | | GATE_INTEGRATION_ID | Yes | Integration ID from the dashboard | | SLACK_BOT_TOKEN | Yes | Bot User OAuth Token (xoxb-...) | | SLACK_APP_TOKEN | Yes | App-Level Token (xapp-...) | | GATE_URL | No | Custom GATE cloud URL | | WEB_PORT | No | Port for the dev dashboard (CLI only) |

Security model

  • Slack tokens stored in .env on YOUR machine
  • GATE cloud never sees or stores your credentials
  • All message content passes through GATE's security pipeline
  • Billing, limits, and security enforced server-side