@commitlint/test

v9.0.1

test utilities for @commitlint For more information about how to use this package see README

Latest version published 4 years 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

67 / 100

Security

Security review needed
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
9.0.1 | 05/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.2.0 | 09/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
7.6.0 | 05/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.1.3 | 03/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.4 | 01/2018
  • 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 (294)

Download trend
GitHub Stars
16.9K
Forks
908
Contributors
250

Direct Usage Popularity

Uncommon

The npm package @commitlint/test receives a total of 294 downloads a week. As such, we scored @commitlint/test popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @commitlint/test, we found that it has been starred 16,904 times.

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

Community

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

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

How about a good first contribution to this project? It seems that @commitlint/test is missing a README file.


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Maintenance

Inactive

Commit Frequency

Open Issues
157
Open PR
20
Last Release
4 years ago
Last Commit
2 days ago

Further analysis of the maintenance status of @commitlint/test 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 @commitlint/test 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.

Package

Node.js Compatibility
>=8

Age
7 years
Dependencies
7 Direct
Versions
17
Install Size
21.5 kB
Dist-tags
2
# of Files
23
Maintainers
4
TS Typings
Yes

@commitlint/test 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.