メニュー
Get detailed metadata for an npm package including versions, dependencies, maintainers, and repository information. Use when the user asks for package details, version history, or package metadata.
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-info |
| description | Get detailed metadata for an npm package including versions, dependencies, maintainers, and repository information. Use when the user asks for package details, version history, or package metadata. |
Retrieve detailed metadata for a specific npm package.
npx tsx scripts/info.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
------
Description: React is a JavaScript library for building user interfaces.
Latest: 18.2.0
License: MIT
Homepage: https://react.dev
Repository: https://github.com/facebook/react
Versions (last 5):
18.2.0 - Published 2022-06-14
18.1.0 - Published 2022-04-26
18.0.0 - Published 2022-03-29
17.0.2 - Published 2021-03-10
17.0.1 - Published 2020-12-20
Maintainers:
- @hzoo
- @acdlite
npx tsx scripts/info.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/
GET https://registry.npmjs.org/{package}
| Parameter | Required | Description |
|---|---|---|
package | Yes | The exact package name (case-sensitive) |
Get package metadata:
https://registry.npmjs.org/react
The response contains comprehensive package metadata:
name - Package nameversions - Object mapping version numbers to full version metadatadist-tags - Tags like latest, next, canarytime - Timestamps for each version publishmaintainers - Array of package maintainersdescription - Package descriptionhomepage - Project homepage URLrepository - Repository information (type, URL)bugs - Bug tracker URL or emaillicense - License identifierauthor - Author informationkeywords - Array of keywordsdependencies - Production dependencies (per version)devDependencies - Development dependencies (per version)peerDependencies - Peer dependencies (per version)The registry accepts various repository URL formats:
https://github.com/owner/repogit+https://github.com/owner/repogit@github.com:owner/repossh://git@github.com/owner/repoThese are automatically parsed and normalized.
Package metadata is cached for 6 hours. Versions change infrequently, and most metadata remains stable between releases.
Use the --no-cache flag to bypass the cache.
npm-search to find packages before getting detailsnpm-exists for a quick availability checknpm-downloads to see usage statisticsPackage not found: If the package doesn't exist, you'll receive a 404 response. Use npm-exists to check availability first.
Invalid package name: Package names must be valid npm package names (lowercase, can contain hyphens, underscores, periods).
Scope issues: For scoped packages like @babel/core, include the scope in the name.