npm-exists

Check whether an npm package name exists in the registry.

3|Updated Jan 17, 2026

Search Tags:#api #npm #validation #registry #exists #package-name

Ready to run

npx skills add https://github.com/Mearman/marketplace --skill npm-exists

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: npm-exists
Source: https://github.com/Mearman/marketplace/tree/main/plugins/npm-registry/skills/npm-exists
Command: npx skills add https://github.com/Mearman/marketplace --skill npm-exists

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Checks whether a given npm package name already exists in the registry to prevent publishing conflicts or wasted time on unavailable names.

Core Features & Use Cases

Existence check: Performs a HEAD request to the npm registry to verify availability for a given package name.
Scope and applicability: Useful before publishing a new package, validating dependencies, or ensuring a desired name is not already taken.
Reliability: Supports cached responses by default and an option to bypass cache for fresh results.

Quick Start

Run the script with a package name to see if it exists in the npm registry.

Frequently Asked Questions about npm-exists

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if an npm package name is available before publishing?▼

To check npm package name availability, perform a HEAD existence request against the npm registry. This instantly verifies whether your desired package name is already taken, preventing publishing conflicts before you attempt to submit it.

How can I verify if an npm package exists in the registry before installing it?▼

You can verify if an npm package exists by running an existence check against the npm registry. This validates whether the specific package name is currently published and available for installation as a dependency.

Does checking npm package existence cache registry responses?▼

Yes, checking npm package existence caches registry responses by default to speed up repeated validation. You can use the --no-cache flag to bypass caching and retrieve fresh existence results directly from the npm registry.

What is the best way to validate npm package names for publishing conflicts?▼

Validating npm package names through a registry existence check is the best way to prevent publishing conflicts. It queries the npm registry directly to ensure the package name is not already published before you proceed.

Can I bypass the cache when checking npm package name availability?▼

Yes, you can bypass the cache when checking npm package name availability by using the optional --no-cache flag. This forces a fresh existence check directly against the npm registry to return real-time availability results.