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

@ashdev/codex-plugin-recommendations-echo

v1.39.2

Published

Echo recommendations plugin for testing and debugging the Codex plugin recommendations protocol

Readme

@ashdev/codex-plugin-recommendations-echo

A minimal test/debug recommendations plugin for the Codex plugin system. It talks to no external service: it echoes your library seeds back as recommendations and records every request and response to files for inspection.

Purpose

  1. Protocol validation - a reference implementation of the recommendation provider protocol (get, updateProfile, clear, dismiss).
  2. Debugging - writes every request/response to JSON files so you can see exactly what the host sends (the library seeds, limit, excluded IDs) without trawling server logs.

Behavior

  • recommendations/get - returns one fully-populated recommendation per library seed, echoing the seed title into reason / basedOn. When the library is empty, returns a few generic recommendations so the result is never empty. Respects the request limit and skips any excludeIds.
  • recommendations/updateProfile - reports the number of entries processed.
  • recommendations/dismiss - acknowledges the dismissal.
  • recommendations/clear - acknowledges the clear.

Payload recording

When recordPayloads is enabled (default), each call writes two JSON files to {dataDir}/payloads/ (the plugin's host-provided data directory):

yyyy-MM-dd-HH-mm-ss-{id}-{method}-request.json
yyyy-MM-dd-HH-mm-ss-{id}-{method}-response.json

Timestamps are UTC, so the files sort chronologically. Each file is a JSON envelope holding the payload plus a snapshot of the active config. Credentials are never written; secret-like config keys are redacted. The number of files is bounded by maxPayloadFiles (oldest pruned). If no data directory is available, files fall back to the OS temp dir.

Configuration

| Key | Default | Description | | ----------------- | ------- | -------------------------------------------------- | | recordPayloads | true | Write request/response files for debugging. | | maxPayloadFiles | 500 | Maximum recorded files to keep; oldest are pruned. |

Development

npm install
npm run build       # bundle to dist/index.js
npm run typecheck
npm run lint
npm test

License

MIT