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

@agentsignalnet/core

v0.2.63

Published

Shared rules behind AgentSignal: message schemas, the endpoints we are willing to fetch, and emergency-priority arithmetic.

Readme

@agentsignalnet/core

Shared types, Zod schemas and validation rules for AgentSignal.

You probably want @agentsignalnet/sdk instead. This package is published because the SDK's public types are built from it — a SendMessageInput in the SDK's signatures is this package's type, so it has to be installable for those signatures to resolve. Installing it directly is supported, but the SDK is the interface.

import { sendMessageSchema } from '@agentsignalnet/core';

Two subpaths exist so a browser bundle can take a rule without taking zod with it:

import { isDeliverableEndpoint } from '@agentsignalnet/core/endpoints';
import { Priority, emergencyRetryFitsExpiry } from '@agentsignalnet/core/priority';

./endpoints is the rule for a URL we will fetch — a public https address, no IP literals, no internal hostnames, no credentials, port 443. It lives here because the schema, the transports and the dashboard all have to apply the same one, and three copies would mean two that are wrong.

./priority holds the emergency bounds and the arithmetic that goes with them, for the same reason: the dashboard has to refuse a retry interval that outlives its own expiry before the API ever sees it.

Licence

Proprietary. See LICENSE — use is permitted for accessing the AgentSignal service, including on the free tier, and not otherwise.