Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Feb 10, 2024 via pnpm

validate-npm-package-name 2.2.2

Give me a string and I'll tell you if it's a valid npm package name
Package summary
Share
0
issues
2
licenses
1
MIT
1
ISC
Package created
12 Nov 2014
Version published
30 Jun 2015
Maintainers
5
Total deps
2
Direct deps
1
License
ISC

Issues

0
This package has no issues

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
builtins@0.0.7

ISC License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
validate-npm-package-name@2.2.2
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

1
All Dependencies CSV
โ“˜ This is a list of validate-npm-package-name 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
builtins0.0.7877 BMIT
prod

Visualizations

Frequently Asked Questions

What does validate-npm-package-name do?

"validate-npm-package-name" is a dynamic npm package that can scrutinize any given string and tell if it's a valid npm package name. It's a piece of code that incorporates a set of rules to validate the given string against typical npm package naming rules. The package exports a synchronous function that takes a string as input and returns an object with two properties: 'validForNewPackages' and 'validForOldPackages'. It becomes quite handy especially for those dealing with new npm package creations as it helps to avoid errors due to invalid package names.

How do you use validate-npm-package-name?

Use of "validate-npm-package-name" is quite simple and intuitive. To initiate it, first, you need to install the package using the command npm install validate-npm-package-name. Once installed, you can then require this package in your code file. From then on, you can use its functionality to validate any given string as an npm package name. Here's a basic code usage example:

var validate = require("validate-npm-package-name");

var result = validate("your-package-name");

console.log(result);

In this example, "your-package-name" is the name you want to validate. The function will return an object with the validity status for new packages as well as old ones.

Where are the validate-npm-package-name docs?

The GitHub repository of "validate-npm-package-name" serves as the main documentation source. You will find all the relevant details regarding the package's functionality, naming rules, and examples. Visit the project's GitHub page at https://github.com/npm/validate-npm-package-name for detailed information. The page not only contains a description of what the package does, but also a clear presentation of how to use it, complete with valid and invalid naming examples. Itโ€™s an exhaustive, well-structured, and easy-to-understand resource for both beginners and experienced JavaScript developers looking to use "validate-npm-package-name".