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

@visitportal/provider

v0.1.9

Published

Optional helper library for Portal providers. Build a validated manifest and serve it over raw fetch-compatible HTTP.

Downloads

402

Readme

@visitportal/provider

Optional helper library for Portal providers. Nothing here you cannot do with raw HTTP; this package exists to kill boilerplate.

What it does

  • Builds a manifest from typed tool definitions
  • Validates the manifest against @visitportal/spec
  • Dispatches { tool, params } requests into your handlers
  • Exposes a fetch-native portal.fetch(request) helper for Edge / Workers / route handlers

Install

npm i @visitportal/provider

Example

import { serve } from "@visitportal/provider";

const portal = serve({
  name: "My Service",
  brief: "One sentence describing what a visiting LLM can do here.",
  call_endpoint: "/portal/call",
  tools: [
    {
      name: "ping",
      description: "returns pong",
      async handler(params) {
        return { pong: true, msg: params.msg ?? null };
      },
    },
  ],
});

export default {
  fetch(request: Request) {
    return portal.fetch(request);
  },
};

If you already have a static portal.json, serve() also accepts { manifest, handlers }.

The reference implementation in reference/trending-demo now uses this package for manifest validation and call dispatch.