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

@aiready/cli

v0.7.13

Published

Unified CLI for AIReady analysis tools

Readme

@aiready/cli

Unified CLI for AIReady analysis tools - Run all AI-readiness checks from a single command

The CLI provides both unified analysis (scan multiple tools at once) and individual tool access for pattern detection, context analysis, and consistency checking.

🚀 Quick Start

Zero config, works out of the box:

# Run without installation (recommended)
npx @aiready/cli scan ./src

# Or install globally for simpler command and faster runs
npm install -g @aiready/cli
aiready scan ./src

🎯 Input & Output

Input: Path to your source code directory

aiready scan ./src

Output: Terminal report + optional JSON file (saved to .aiready/ directory)

📊 AIReady Scan Results
━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔍 Pattern Detection
   📁 Files analyzed: 47
   ⚠️  Duplicate patterns: 12 files with 23 issues
   💰 Wasted tokens: 8,450

📦 Context Analysis
   📁 Files analyzed: 47
   ⚠️  High context cost: 8 files
   🔗 Deep import chains: 5 files

✨ Smart Defaults (Zero Config)

  • Auto-excludes test files (**/*.test.*, **/*.spec.*, **/__tests__/**)
  • Auto-excludes build outputs (dist/, build/, .next/, cdk.out/)
  • Auto-excludes dependencies (node_modules/)
  • Adaptive thresholds: Adjusts issue detection based on codebase size
  • Unified reporting: Combines results from all tools into one view

Override defaults with --include or --exclude options as needed

📦 Commands

Unified Scan

Run multiple analysis tools in one command:

aiready scan <directory>

Options:

  • -t, --tools <tools>: Tools to run (comma-separated: patterns,context,consistency) (default: patterns,context)
  • --include <patterns>: File patterns to include (comma-separated)
  • --exclude <patterns>: File patterns to exclude (comma-separated)
  • -o, --output <format>: Output format: console, json (default: console)
  • --output-file <path>: Output file path (defaults to .aiready/aiready-scan-YYYY-MM-DD.json)

Individual Tools

Access each tool directly for focused analysis:

Pattern Detection

aiready patterns <directory> [options]

Options:

  • -s, --similarity <number>: Minimum similarity score (0-1) (default: 0.40)
  • -l, --min-lines <number>: Minimum lines to consider (default: 5)
  • --include <patterns>: File patterns to include (comma-separated)
  • --exclude <patterns>: File patterns to exclude (comma-separated)
  • -o, --output <format>: Output format: console, json (default: console)
  • --output-file <path>: Output file path (defaults to .aiready/pattern-report-YYYY-MM-DD.json)

Context Analysis

aiready context <directory> [options]

Options:

  • --max-depth <number>: Maximum acceptable import depth (default: 5)
  • --max-context <number>: Maximum acceptable context budget (tokens) (default: 10000)
  • --include <patterns>: File patterns to include (comma-separated)
  • --exclude <patterns>: File patterns to exclude (comma-separated)
  • -o, --output <format>: Output format: console, json (default: console)
  • --output-file <path>: Output file path (defaults to .aiready/context-report-YYYY-MM-DD.json)

Consistency Analysis

aiready consistency <directory> [options]

Options:

  • --include <patterns>: File patterns to include (comma-separated)
  • --exclude <patterns>: File patterns to exclude (comma-separated)
  • -o, --output <format>: Output format: console, json (default: console)
  • --output-file <path>: Output file path (defaults to .aiready/consistency-report-YYYY-MM-DD.json)

📁 Output Files: By default, all output files are saved to the .aiready/ directory in your project root with timestamped filenames. You can override this with --output-file.

💡 Examples

Basic Usage

# Analyze current directory with all tools
aiready scan .

# Run specific tools only
aiready scan . --tools patterns,context

# Analyze only patterns
aiready patterns .

# Analyze only context costs
aiready context .

# Analyze only consistency
aiready consistency .

Advanced Usage

# Analyze specific file types
aiready scan ./src --include "**/*.ts,**/*.js"

# Exclude test files
aiready scan . --exclude "**/*.test.*,**/*.spec.*"

# Save results to JSON file (.aiready/ directory by default)
aiready scan . --output json

# Save to custom location
aiready scan . --output json --output-file custom-results.json

# Run only pattern analysis with custom similarity threshold
aiready patterns . --similarity 0.6 --min-lines 10

# Run context analysis with custom thresholds
aiready context . --max-depth 3 --max-context 5000

⚙️ Configuration

AIReady supports configuration files to persist your settings. Create one of these files in your project root:

  • aiready.json
  • aiready.config.json
  • .aiready.json
  • .aireadyrc.json
  • aiready.config.js
  • .aireadyrc.js

Example Configuration

{
  "scan": {
    "include": ["**/*.{ts,tsx,js,jsx}"],
    "exclude": ["**/test/**", "**/*.test.*", "**/*.spec.*"]
  },
  "tools": {
    "pattern-detect": {
      "minSimilarity": 0.5,
      "minLines": 8,
      "approx": false
    },
    "context-analyzer": {
      "maxDepth": 4,
      "maxContextBudget": 8000,
      "includeNodeModules": false
    }
  },
  "output": {
    "format": "console",
    "file": "aiready-report.json"
  }
}

Configuration values are merged with defaults, and CLI options take precedence over config file settings.

🔄 CI/CD Integration

# JSON output for automated processing
aiready scan . --output json --output-file aiready-results.json

# Exit with error code if issues found
aiready scan . && echo "No issues found" || echo "Issues detected"

📊 Output Formats

Console Output

Human-readable summary with key metrics and issue counts.

JSON Output

Structured data including:

  • Full analysis results
  • Detailed metrics
  • Issue breakdowns
  • Execution timing

🚦 Exit Codes

  • 0: Success, no critical issues
  • 1: Analysis failed or critical issues found

🔗 Integration

The CLI is designed to integrate with:

  • CI/CD pipelines
  • Pre-commit hooks
  • IDE extensions
  • Automated workflows

For programmatic usage, see the individual packages:

🌐 Visit Our Website

Try AIReady tools online and learn more: getaiready.dev