メニュー
Analyze npm package quality using NPMS.io scores for quality, popularity, and maintenance. Use when the user asks for package quality analysis, NPMS scores, or package evaluation metrics.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | npms-analyze |
| description | Analyze npm package quality using NPMS.io scores for quality, popularity, and maintenance. Use when the user asks for package quality analysis, NPMS scores, or package evaluation metrics. |
Analyze an npm package using NPMS.io quality, popularity, and maintenance scores.
npx tsx scripts/analyze.ts <package-name> [options]
| Argument | Required | Description |
|---|---|---|
package-name | Yes | The exact package name (case-sensitive) |
| Option | Description |
|---|---|
--no-cache | Bypass cache and fetch fresh data from API |
react - Package Analysis
-------------------------
Quality Scores:
Overall: 98/100
Quality: 95/100
Popularity: 100/100
Maintenance: 99/100
Package Information:
Version: 18.2.0
Description: A declarative, efficient, and flexible JavaScript library...
Published: 2013-05-24
npm Statistics:
Week: 2,345,678 downloads
Month: 9,876,543 downloads
Year: 98,765,432 downloads
GitHub Activity:
Stars: 213,456
Forks: 45,678
Open Issues: 1,234
Contributors: 1,567
Latest Commit: 2 days ago
Project Health:
✓ Has contributing guide
✓ Has license
✓ Has security policy
npx tsx scripts/analyze.ts <package-name> [options]
Options:
--no-cache - Bypass cache and fetch fresh data from APIRun from the npms-io plugin directory: ~/.claude/plugins/cache/npms-io/
GET https://api.npms.io/v2/package/{package}
| Parameter | Required | Description |
|---|---|---|
package | Yes | The exact package name (case-sensitive) |
Get package analysis:
https://api.npms.io/v2/package/react
The response contains comprehensive package analysis:
name, version, description, keywordsdownloads - Download counts over timeweekDownloads, monthDownloads, quarterDownloads, yearDownloadsstars, forks, subscribersissues (open, closed, total)pull requests (open, closed, total)contributors, commitCountlatestCommit (sha, date, message)recentReleases, firstRelease, latestReleasefinal - Overall scorequality - Code quality assessmentpopularity - Community adoptionmaintenance - Project maintenance statusPackage analysis is cached for 6 hours. NPMS.io data updates relatively infrequently, and package metrics change slowly over time.
Use the --no-cache flag to bypass the cache.
npms-compare to compare multiple packages side-by-sidenpms-suggest to find similar packages by namenpm-info for detailed package metadatanpm-downloads for download statisticsPackage not found: The package may not exist in NPMS.io database. New packages may take time to be analyzed.
Incomplete analysis: Some packages may lack GitHub integration or download data, resulting in partial scores.
Analysis pending: Newly published packages may not have completed analysis. Check back later.
| Score Range | Quality Level | Recommendation |
|---|---|---|
| 90-100 | Excellent | Safe to use, well-maintained |
| 75-89 | Good | Generally reliable |
| 60-74 | Fair | Use with caution, review dependencies |
| 0-59 | Poor | Avoid, look for alternatives |
Compare alternatives before choosing:
npx tsx scripts/analyze.ts express
npx tsx scripts/analyze.ts koa
npx tsx scripts/analyze.ts fastify
Check your dependencies:
npx tsx scripts/analyze.ts lodash
npx tsx scripts/analyze.ts axios
Evaluate new packages:
npx tsx scripts/analyze.ts new-popular-package
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.