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

@devradardev/cli

v1.0.1

Published

CLI tool for DevRadar - Check your tech stack compatibility from the terminal

Readme

@devradar-dev/cli

Check your tech stack compatibility from the terminal

npm version License: MIT

Installation

npm install -g @devradar-dev/cli

Or use with npx (no installation required):

npx @devradar-dev/cli check nextjs prisma

Usage

Check Compatibility

Check if two technologies work well together:

devradar check nextjs prisma

Output:

Nextjs + Prisma
────────────────────────────────────────
✓ Compatible

Compatible in Node.js runtime but does NOT work in Edge Runtime.

→ Learn more: https://devradar.dev/check/nextjs-prisma

Scan package.json

Analyze your entire project for compatibility issues:

# Scan current directory
devradar scan

# Scan specific project
devradar scan ./my-app/package.json

Output:

Stack Compatibility Scan
────────────────────────────────────────
Score: 55/100

Detected Technologies:
  ✓ Nextjs
  ✓ Prisma
  ✓ Tailwind

Issues (1):
  1. Nextjs + Prisma
     [WARNING] Edge Runtime incompatibility detected

Suggestions:
  • Consider using Turso or PlanetScale for Edge-compatible database
    https://devradar.dev/check/prisma-vercel-edge

Scanned: 5 dependencies

Options

JSON Output

Get machine-readable output for CI/CD:

devradar check nextjs prisma --json
devradar scan --json

Response:

{
  "techA": "nextjs",
  "techB": "prisma",
  "version": "1.0",
  "status": "partial",
  "severity": "warning",
  "message": "...",
  "workaround": "...",
  "docsUrl": "https://devradar.dev/check/nextjs-prisma"
}

Help

devradar --help
devradar check --help
devradar scan --help

Version

devradar --version

Exit Codes

| Code | Meaning | |------|---------| | 0 | Compatible / Good score (60+) | | 1 | Partial compatibility / Medium score (40-59) | | 2 | Incompatible / Poor score (<40) |

Use in CI/CD:

devradar check nextjs prisma || echo "Compatibility issues found!"

Examples

CI/CD Integration

# .github/workflows/compatibility-check.yml
- name: Check tech stack compatibility
  run: npx @devradar-dev/cli scan --json > compatibility-report.json

Pre-commit Hook

# .git/hooks/pre-commit
devradar scan || exit 1

Dockerfile Check

devradar check node alpine
devradar check nextjs vercel-edge

API

The CLI uses DevRadar's public API:

  • Check API: POST /api/v1/check
  • Scan API: POST /api/v1/scan

Rate limits:

  • Check: 60 requests/minute
  • Scan: 10 requests/minute

Development

Local Testing

# Clone repo
git clone https://github.com/devradar-dev/cli.git
cd cli

# Install dependencies
npm install

# Link for local testing
npm link

# Test
devradar check nextjs prisma
devradar scan

Project Structure

@devradar-dev/cli/
├── bin/
│   └── devradar.js          # CLI entry point
├── src/
│   ├── api/
│   │   └── client.ts        # API client
│   ├── commands/
│   │   ├── check.ts         # Check command
│   │   └── scan.ts          # Scan command
│   └── output/
│       ├── text.ts          # Terminal output
│       └── json.ts          # JSON output
├── package.json
└── README.md

Deployment

Publish to npm

# Build (if needed)
npm run build

# Publish to @devradar-dev org
npm publish --access public

GitHub Repository

  1. Create new repo: github.com/devradar-dev/cli
  2. Push code:
    git remote add origin https://github.com/devradar-dev/cli.git
    git branch -M main
    git push -u origin main

License

MIT © DevRadar

Links

  • Website: https://devradar.dev
  • Documentation: https://github.com/devradar-dev/cli/wiki
  • API Docs: https://devradar.dev/api
  • Report Issues: https://github.com/devradar-dev/cli/issues

Made with ❤️ for developers worldwide