القائمة
Check if an npm package name exists in the registry. Use when the user asks if a package name is available, wants to check package existence, or verify if a package is published.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | npm-exists |
| description | Check if an npm package name exists in the registry. Use when the user asks if a package name is available, wants to check package existence, or verify if a package is published. |
Check if a package name exists in the npm registry.
npx tsx scripts/exists.ts <package-name> [options]
| Argument | Required | Description |
|---|---|---|
package-name | Yes | The exact package name to check (case-sensitive) |
| Option | Description |
|---|---|
--no-cache | Bypass cache and fetch fresh data from API |
Package exists:
✓ Package "react" exists
URL: https://www.npmjs.com/package/react
Published: Yes
Package does not exist:
✗ Package "my-awesome-pkg-12345" does not exist
The name is available for use
npx tsx scripts/exists.ts <package-name> [options]
Options:
--no-cache - Bypass cache and fetch fresh data from APIRun from the npm-registry plugin directory: ~/.claude/plugins/cache/npm-registry/
HEAD https://registry.npmjs.org/{package}
| Parameter | Required | Description |
|---|---|---|
package | Yes | The exact package name to check (case-sensitive) |
Check if a package exists:
HEAD https://registry.npmjs.org/react
For scoped packages:
HEAD https://registry.npmjs.org/@babel/core
Package exists - HTTP 200 OK
npm info or npm install with this namePackage does not exist - HTTP 404 Not Found
Before publishing a new package, verify the name is available:
npx tsx exists.ts my-new-package
Confirm a package exists before installing or using it:
npx tsx exists.ts some-dependency
Check scoped package names:
npx tsx exists.ts @myorg/package-name
Package names must:
@, or _. or _Scoped packages (@scope/name) have additional rules:
Existence checks are cached for 1 hour. Package availability changes infrequently, so short cache times provide a good balance between freshness and performance.
Use the --no-cache flag to bypass the cache.
npm-info to get detailed package metadata when it existsnpm-search to find similar or alternative packagesnpm-downloads to see package statisticsNetwork errors: The npm registry may be temporarily unavailable. Retry after a brief delay.
Rate limiting: While existence checks use HEAD requests (minimal bandwidth), excessive rapid requests may be rate-limited.
Scoped packages: Remember that scoped packages require the full name including the scope (e.g., @babel/core, not just core).