@webex/internal-plugin-mercury

v3.5.0

undefined For more information about how to use this package see README

Latest version published 27 days 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

84 / 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
2.60.4 | 10/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.5.0 | 10/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.4.0 | 09/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.161.0 | 05/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.59.0 | 06/2019
Popular
  • 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 (10,021)

Download trend
GitHub Stars
173
Forks
344
Contributors
120

Direct Usage Popularity

Occasionally

The npm package @webex/internal-plugin-mercury receives a total of 10,021 downloads a week. As such, we scored @webex/internal-plugin-mercury popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package @webex/internal-plugin-mercury, we found that it has been starred 173 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
No
Contributors
120
Funding
No

A good and healthy external contribution signal for @webex/internal-plugin-mercury 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 @webex/internal-plugin-mercury is missing a Code of Conduct.

How about a good first contribution to this project? It seems that @webex/internal-plugin-mercury is missing a README file.


Embed Package Health Score Badge

package health: 84/100 package health 84/100

Maintenance

Healthy

Commit Frequency

Open Issues
6
Open PR
35
Last Release
27 days ago
Last Commit
1 day ago

Further analysis of the maintenance status of @webex/internal-plugin-mercury based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @webex/internal-plugin-mercury demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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
>=16

Age
5 years
Dependencies
16 Direct
Versions
1.24K
Install Size
254 kB
Dist-tags
6
# of Files
37
Maintainers
7
TS Typings
No

@webex/internal-plugin-mercury 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.