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

@stefkec/agent-ready

v0.3.1

Published

Scan sites for agent readiness and scaffold framework-specific machine-readable endpoints.

Readme

agent-ready

npm version npm downloads CI codecov license node

agent-ready is a TypeScript-first CLI and library for scanning agent-readiness signals and scaffolding framework-specific machine-readable endpoints.

What it does

  • Scans live sites against an agent-readiness surface modeled on isitagentready.com
  • Inspects local projects with framework-aware path and route conventions
  • Scaffolds agent-facing files and endpoints for supported JavaScript/TypeScript frameworks
  • Supports CI-friendly exit behavior with score and status thresholds

Install

npm install @stefkec/agent-ready

Or run it directly:

npx @stefkec/agent-ready scan https://example.com

CLI

agent-ready scan <url> [--json] [--report-file <path>] [--min-score <n>] [--fail-on-status <list>]
agent-ready doctor [cwd] [--cwd <path>] [--json] [--report-file <path>] [--min-score <n>] [--fail-on-status <list>]
agent-ready init [--cwd <path>] [--framework <name>] [--preset <name>] [--features <list>] [--dry-run] [--json] [--report-file <path>]
agent-ready add <feature> [--cwd <path>] [--json] [--report-file <path>]
agent-ready explain <check>

Examples

Scan a live site:

npx agent-ready scan https://example.com

Scan a live site and fail CI on warnings or failures:

npx agent-ready scan https://example.com --min-score 80 --fail-on-status warn,fail

Write a JSON report artifact:

npx agent-ready doctor --json --report-file ./reports/agent-ready.json

Inspect a local project:

npx agent-ready doctor

Scaffold a Next.js project:

npx agent-ready init --framework next

Scaffold an application-style project:

npx agent-ready init --framework express --preset application

Scaffold an exact feature set:

npx agent-ready init --framework next --features robots,llms,mcp

Scaffold into another directory:

npx agent-ready init --cwd ./apps/web --framework next --preset content-site

Add only an MCP server card scaffold:

npx agent-ready add mcp

Config file

Supported config files:

  • agent-ready.config.json
  • agent-ready.config.mjs
  • agent-ready.config.cjs

Example:

{
  "defaults": {
    "output": "human"
  },
  "scan": {
    "minScore": 80,
    "failOnStatuses": ["warn", "fail"]
  },
  "doctor": {
    "minScore": 75,
    "failOnStatuses": ["fail", "error"]
  },
  "init": {
    "framework": "next",
    "preset": "content-site",
    "features": ["api-catalog", "robots", "sitemap", "llms", "mcp"]
  }
}

Config is optional. CLI flags still take precedence.

Presets

  • content-site Intended for marketing sites, docs sites, and content-heavy apps.
  • application Intended for API-capable apps and authenticated products.

Default behavior:

  • next, astro, sveltekit, nuxt, vite-react, and vite-vue default to content-site
  • express and hono default to application

Supported scaffold features

  • api-catalog
  • robots
  • sitemap
  • llms
  • markdown
  • mcp
  • agent-card
  • oauth-discovery
  • oauth-protected-resource

Supported frameworks

  • next
  • astro
  • sveltekit
  • express
  • hono
  • nuxt
  • vite-react
  • vite-vue

Framework support is uneven right now. next, astro, sveltekit, express, and hono have the strongest scaffold behavior.

TypeScript usage

import { scanSite, scaffoldProject, scanProject } from "agent-ready";

const report = await scanSite({ url: "https://example.com" });

const local = await scanProject({ cwd: process.cwd() });

await scaffoldProject({
  cwd: process.cwd(),
  framework: "next",
  features: ["api-catalog", "robots", "llms", "mcp"]
});

CI example

npx agent-ready doctor --min-score 80 --fail-on-status fail,error
npx agent-ready scan https://example.com --min-score 85 --fail-on-status warn,fail,error

Development

npm install
npm run check
npm run test
npm run build