all-the-package-names

v2.0.1873

A list of all the public package names on npm. Updated daily. For more information about how to use this package see README

Latest version published 9 hours 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

65 / 100

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
2.0.1873 | 11/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.1452 | 04/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3905.0 | 11/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3855.0 | 09/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3854.0 | 09/2019
  • 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

Small

Weekly Downloads (1,438)

Download trend
GitHub Stars
245
Forks
28
Contributors
6

Direct Usage Popularity

Uncommon

The npm package all-the-package-names receives a total of 1,438 downloads a week. As such, we scored all-the-package-names popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package all-the-package-names, we found that it has been starred 245 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
6
Funding
Yes

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 65/100 package health 65/100

Maintenance

Sustainable

Commit Frequency

Open Issues
4
Open PR
4
Last Release
9 hours ago
Last Commit
2 days ago

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

We found that all-the-package-names demonstrates a positive version release cadence with at least one new version released in the past 3 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
not defined

Age
10 years
Dependencies
0 Direct
Versions
5.78K
Install Size
85.9 MB
Dist-tags
1
# of Files
10
Maintainers
1
TS Typings
Yes

all-the-package-names 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.