القائمة
Search for npm packages by keyword, name, or description. Use when the user asks to search npm packages, find packages related to a topic, or discover packages for a specific purpose.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | npm-search |
| description | Search for npm packages by keyword, name, or description. Use when the user asks to search npm packages, find packages related to a topic, or discover packages for a specific purpose. |
Search the npm registry for packages by keyword, name, or description.
npx tsx scripts/search.ts <query> [options]
| Argument | Required | Description |
|---|---|---|
query | Yes | Search query (can be package name, keyword, or description text) |
| Option | Description |
|---|---|
--size=N | Number of results to return (default: 20, max: 250) |
--from=N | Offset for pagination (default: 0) |
--no-cache | Bypass cache and fetch fresh data from API |
Found 1,234 packages for "http"
1. express (4.18.2)
Fast, unopinionated, minimalist web framework
Score: 0.98 (quality: 0.95, popularity: 1.0, maintenance: 0.99)
https://www.npmjs.com/package/express
2. axios (1.6.0)
Promise based HTTP client for the browser and node.js
Score: 0.97 (quality: 0.94, popularity: 1.0, maintenance: 0.98)
https://www.npmjs.com/package/axios
npx tsx scripts/search.ts <query> [options]
Options:
--size=N - Number of results to return (default: 20, max: 250)--from=N - Offset for pagination (default: 0)--no-cache - Bypass cache and fetch fresh data from APIRun from the npm-registry plugin directory: ~/.claude/plugins/cache/npm-registry/
GET https://registry.npmjs.org/-/v1/search
| Parameter | Required | Type | Description |
|---|---|---|---|
text | Yes | string | Search query (can be package name, keyword, or description text) |
size | No | number | Number of results to return (default: 20, max: 250) |
from | No | number | Offset for pagination (default: 0) |
Search for HTTP-related packages:
https://registry.npmjs.org/-/v1/search?text=http&size=10
Search with pagination:
https://registry.npmjs.org/-/v1/search?text=react&size=20&from=20
Each result contains:
package.name - Package namepackage.version - Latest versionpackage.description - Package descriptionpackage.keywords - Array of keywords (if available)package.author - Author informationpackage.links - URLs to npm, homepage, repository, bugsscore.final - Overall score (0-1)score.detail.quality - Quality score (0-1)score.detail.popularity - Popularity score (0-1)score.detail.maintenance - Maintenance score (0-1)searchScore - Relevance to search querySearch results are cached for 1 hour. The npm registry search index is updated frequently but package metadata changes less often.
Use the --no-cache flag to bypass the cache and fetch fresh results.
npm-info to get detailed package metadatanpm-exists to quickly check if a package name is availablenpm-downloads to view download statisticsIf the search returns no results, try:
Rate limiting: The npm registry may rate limit excessive requests. If you encounter rate limiting, wait a few minutes before trying again.
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.