メニュー
Compare multiple npm packages side-by-side using NPMS.io quality scores. Use when the user asks to compare packages, evaluate alternatives, or choose between multiple options.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when the user needs help with path queries, JSON transformations, schema validation, or safe JSON editing workflows. Triggered by questions about JSON operations, data extraction, file merging, or validation strategies.
Scan project dependencies for known vulnerabilities. Automatically detect and parse package files (package.json, requirements.txt, Gemfile, go.mod, pom.xml) and check all dependencies against the CVE database. Use when you want to audit a project for security vulnerabilities, check if dependencies have known CVEs, or generate a vulnerability report for compliance.
Search for Common Vulnerabilities and Exposures (CVEs) by ID (e.g., CVE-2024-1086) or by product name (e.g., OpenSSL, Apache Tomcat). Get detailed vulnerability information including severity scores, affected software versions, and references. Use when the user wants to look up CVE information, check if a product has known vulnerabilities, or research security issues.
Validate a JSON file against the schema referenced in its $schema property. Use when the user asks to check JSON against its own schema, validate self-describing JSON, auto-validate JSON files, or verify JSON with embedded schema reference.
Validate JSON data against a JSON Schema. Use when the user asks to validate JSON against a schema, check if JSON conforms to a schema, test JSON data validity, or verify JSON structure matches a schema definition.
Validate that a JSON Schema is well-formed and conforms to the JSON Schema specification. Use when the user asks to check if a schema is valid, verify schema syntax, validate schema structure, or check a JSON Schema file for errors.
SOC 職業分類に基づく
| name | npms-compare |
| description | Compare multiple npm packages side-by-side using NPMS.io quality scores. Use when the user asks to compare packages, evaluate alternatives, or choose between multiple options. |
Compare multiple npm packages side-by-side using NPMS.io quality scores.
npx tsx scripts/compare.ts <package1> <package2> [package3...] [options]
| Argument | Required | Description |
|---|---|---|
package1 | Yes | First package to compare |
package2 | Yes | Second package to compare |
package3... | No | Additional packages to compare |
| Option | Description |
|---|---|
--no-cache | Bypass cache and fetch fresh data from API |
Package Comparison: react vs vue vs angular
-------------------------------------------
┌──────────────┬──────────┬──────────┬──────────┐
│ Metric │ react │ vue │ angular │
├──────────────┼──────────┼──────────┼──────────┤
│ Overall │ 98/100 │ 95/100 │ 92/100 │
│ Quality │ 95/100 │ 93/100 │ 90/100 │
│ Popularity │ 100/100 │ 97/100 │ 95/100 │
│ Maintenance │ 99/100 │ 96/100 │ 91/100 │
├──────────────┼──────────┼──────────┼──────────┤
│ Version │ 18.2.0 │ 3.3.4 │ 16.2.0 │
│ Stars │ 213K │ 204K │ 92K │
│ Forks │ 45K │ 34K │ 25K │
│ Issues │ 1.2K │ 890 │ 1.5K │
│ Downloads/Mo │ 9.8M │ 3.2M │ 2.1M │
└──────────────┴──────────┴──────────┴──────────┘
npx tsx scripts/compare.ts <package1> <package2> [package3...] [options]
Options:
--no-cache - Bypass cache and fetch fresh data from APIRun from the npms-io plugin directory: ~/.claude/plugins/cache/npms-io/
POST https://api.npms.io/v2/package/mget
Content-Type: application/json
["package1", "package2", "package3"]
| Parameter | Required | Description |
|---|---|---|
packages | Yes | Array of package names (JSON array in POST body) |
Compare packages:
curl -X POST https://api.npms.io/v2/package/mget \\
-H "Content-Type: application/json" \\
-d '["react", "vue", "angular"]'
The response contains analysis data for each requested package:
{
"react": { /* NpmsPackage */ },
"vue": { /* NpmsPackage */ },
"angular": { /* NpmsPackage */ }
}
Packages that don't exist or haven't been analyzed will have null values.
The comparison includes:
Scores (0-100)
Package Info
GitHub Stats
npm Stats
Project Health
Comparison results are cached for 6 hours. Package metrics change slowly, so cached data remains accurate for extended periods.
Use the --no-cache flag to bypass the cache.
npms-analyze for detailed analysis of a single packagenpms-suggest to find packages by name patternnpm-search to find packages by keywordSome packages not found: The comparison will show available data for found packages and note which ones were missing.
All packages not found: Verify package names are correct. New packages may take time to be analyzed.
Rate limiting: NPMS.io may rate limit excessive requests. Cache results to reduce API calls.
Choose the package with the highest overall score if all other factors are equal.
Higher scores indicate active development and recent updates.
Higher downloads indicate wider adoption but not necessarily better quality.
Compare JavaScript frameworks:
npx tsx scripts/compare.ts react vue angular
Compare similar libraries:
npx tsx scripts/compare.ts axios got node-fetch
Compare state management solutions:
npx tsx scripts/compare.ts redux zustand pinia
Compare CSS-in-JS libraries:
npx tsx scripts/compare.ts styled-components emotion linaria