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

@rtrvr-ai/site-intel

v0.2.9

Published

Runtime-agnostic core for turning captured web traffic into ranked API endpoints, replayable recipes, and trust-scored agent capabilities. Single source of truth shared by rtrvr-relay, extension-use, rtrvr-web-agent, rtrvr-cloud-backend, and rover-scout-w

Vulnerabilities

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

Links

Git

Maintainers

bhavanikalisettybhavanikalisetty

Keywords

rtrvrroversite-intelnetwork-recipeapi-discoveryagentic-commerce

Readme

@rtrvr-ai/site-intel

Runtime-agnostic core for turning captured web traffic into ranked API endpoints, replayable recipes, and trust-scored agent capabilities.

This is the shared foundation described in the Rover Scout ground-up revamp. It exists so that the network-tool "capture → evidence → cluster → classify → provenance → recipe → verify → trust" pipeline lives in exactly one place instead of the four divergent copies that exist today (rtrvr-relay original, rtrvr-cloud-backend prompt side, extension-use snapshot, rtrvr-web-agent backend half, plus rover-scout-worker's own lineage).

Layout & runtime scoping

Entrypoints are runtime-scoped so a browser bundle never pulls Node/CDP code:

  • @rtrvr-ai/site-intel/core — isomorphic. No capture, no LLM calls, no CDP. Pure functions over the NetworkExchange model: templating, clustering, scoring (rank-only, no silent drop-gate), response-shape hints, JSON-Schema inference, secret redaction, the acorn AST runner validator, and the Unbrowse-style composite trust score. node:crypto is used for stable hashing; browser consumers polyfill it (a P10 concern when relay/ extension-use migrate).
  • @rtrvr-ai/site-intel/capture — capture adapters behind a CaptureAdapter seam (HAR today; webRequest / main-world / CDP adapters land as the other repos migrate).
  • . (root) re-exports both.

Where this package lives

It is a workspace package inside the rover-scout-worker monorepo so that Scout — its first consumer — can iterate against it with a pnpm workspace link. It publishes to npm (like @rtrvr-ai/rover-scout-core) so rtrvr-relay / rtrvr-web-agent / extension-use can depend on the published version later. Nothing about the public API assumes this location; it can be extracted to its own repo without an API change.

Core principle: static tables are EVIDENCE, never GATES

The cheap provider/keyword/URL heuristics survive here as advisory signals attached to endpoint clusters. They rank and tag; they never silently drop a candidate. "Nothing found" is a quality-gate signal for the caller to surface, not an empty success.