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/abuse

v0.0.3

Published

Composable abuse, moderation, and reach policy decisions for xNet

Readme

@xnetjs/abuse

Composable abuse, moderation, and reach policy decisions for xNet.

This package is intentionally dependency-light so lower-level packages such as @xnetjs/sync, @xnetjs/network, and @xnetjs/hub can adopt the decision types without depending on @xnetjs/data.

Core Idea

Adapters gather facts. Pure functions make decisions.

import { decidePublicInteraction } from '@xnetjs/abuse'

const decision = decidePublicInteraction({
  actor: { firstContact: true },
  labels: [{ value: 'spam', confidence: 0.6, sourceWeight: 1, sourceDID: 'did:key:z...' }],
  quality: { slopScore: 0.4 }
})

console.log(decision.admission) // "quarantine"

Current Scope

  • Shared decision/result types
  • Deterministic reason codes
  • Pure decision helpers for transport, remote mutation, public interaction, and reach
  • Adapter helpers under @xnetjs/abuse/adapters
  • Explanation helpers for UI/devtools/audit surfaces
  • Fixtures for tests and future package adapters

Adapter Entry Point

Protocol packages should keep their local verification, rate-limit, and scoring code local, then adapt the result into shared abuse facts:

import { createRemoteAdmissionPipeline } from '@xnetjs/abuse/adapters'

const pipeline = createRemoteAdmissionPipeline({
  adapt: (event: { signatureValid: boolean; overSizeLimit: boolean; peerScore: number }) => ({
    surface: 'remoteMutation',
    crypto: {
      signatureValid: event.signatureValid
    },
    resource: {
      overSizeLimit: event.overSizeLimit
    },
    actor: {
      peerScore: event.peerScore
    }
  })
})

const result = pipeline.evaluate({
  signatureValid: false,
  overSizeLimit: false,
  peerScore: 100
})

console.log(result.shouldMutate) // false

Signed moderation schemas live in future @xnetjs/data work so this package can stay safe for lower-level imports.