package-name-regex

v4.0.0

Provides a regex that can be used to test if a string is a valid NPM package name. For more information about how to use this package see README

Latest version published 10 months ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

58 / 100

Explore Similar Packages

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
4.0.0 | 03/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.1 | 11/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.6 | 01/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.14 | 04/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (73,245)

Download trend
GitHub Stars
5
Forks
0
Contributors
8

Direct Usage Popularity

TOP 30%

The npm package package-name-regex receives a total of 73,245 downloads a week. As such, we scored package-name-regex popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package package-name-regex, we found that it has been starred 5 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
8
Funding
Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like package-name-regex is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive

Commit Frequency

Open Issues
1
Open PR
4
Last Release
10 months ago
Last Commit
1 month ago

Further analysis of the maintenance status of package-name-regex based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that package-name-regex demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>=18

Age
5 years
Dependencies
0 Direct
Versions
27
Install Size
6.58 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

package-name-regex has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.