@types/pluralize

v0.0.29

TypeScript definitions for pluralize

MIT
Latest version published 3 years ago
    npm install @types/pluralize
  
We couldn't find any similar packages Browse all packages

Package Health Score

71 / 100

Popularity

Influential project

Weekly Downloads (303,078)

Download trend
Dependents
365
GitHub Stars
35.74K
Forks
25.7K
Contributors
410

Direct Usage Popularity

TOP 5%

The npm package @types/pluralize receives a total of 303,078 downloads a week. As such, we scored @types/pluralize popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @types/pluralize, we found that it has been starred 35,745 times, and that 365 other projects in the ecosystem are dependent on it.

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

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

07/2018

Direct Vulnerabilities

Popular
0.0.29
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.0.29
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
0.0.29
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like @types/pluralize is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test @types/pluralize
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
530
Open PR
185
Last Release
3 years ago
Last Commit
11 hours ago

Further analysis of the maintenance status of @types/pluralize based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @types/pluralize is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Active
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
410
Funding
No

A good and healthy external contribution signal for @types/pluralize project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like @types/pluralize is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 71/100 package health 71/100

Package

Node.js Compatibility
not defined

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

@types/pluralize 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.