mercury

v14.2.0

A truly modular frontend framework For more information about how to use this package see README

Latest version published 2 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

51 / 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
14.2.0 | 06/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
14.1.0 | 02/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
13.0.0 | 02/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
12.0.0 | 12/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.1.0 | 12/2014
  • 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 (247)

Download trend
Dependents
34
GitHub Stars
2.83K
Forks
174
Contributors
40

Direct Usage Popularity


The npm package mercury receives a total of 247 downloads a week. As such, we scored mercury popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package mercury, we found that it has been starred 2,833 times, and that 34 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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
40
Funding
No

With more than 10 contributors for the mercury repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like mercury is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
33
Open PR
0
Last Release
2 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of mercury 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 mercury 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.

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
11 years
Dependencies
12 Direct
Versions
56
Install Size
330 kB
Dist-tags
1
# of Files
107
Maintainers
2
TS Typings
No

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.