validate-npm-package-name
Advanced tools
Comparing version 2.0.0 to 2.0.1
{ | ||
"name": "validate-npm-package-name", | ||
"version": "2.0.0", | ||
"version": "2.0.1", | ||
"description": "Give me a string and I'll tell you if it's a valid npm package name", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -8,3 +8,3 @@ # validate-npm-package-name | ||
### Valid Names | ||
## Valid Names | ||
@@ -32,3 +32,3 @@ ```js | ||
### Invalid Names | ||
## Invalid Names | ||
@@ -52,3 +52,3 @@ ```js | ||
### Legacy Names | ||
## Legacy Names | ||
@@ -55,0 +55,0 @@ In the old days of npm, package names were wild. They could have capital |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
8310