m-tree

v0.0.7

Construct Merkle Trees and verify proofs For more information about how to use this package see README

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

54 / 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
0.0.7 | 07/2018
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

Limited

Weekly Downloads (1)

Download trend
GitHub Stars
1.16K
Forks
206
Contributors
30

Direct Usage Popularity


The npm package m-tree receives a total of 1 downloads a week. As such, we scored m-tree popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package m-tree, we found that it has been starred 1,163 times.

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
30
Funding
Yes

With more than 10 contributors for the m-tree 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 m-tree is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Maintenance

Inactive

Commit Frequency

Open Issues
17
Open PR
2
Last Release
6 years ago
Last Commit
4 months ago

Further analysis of the maintenance status of m-tree 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 m-tree 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
>= 7.6.0

Age
7 years
Dependencies
1 Direct
Versions
7
Install Size
250 kB
Dist-tags
1
# of Files
17
Maintainers
1
TS Typings
No

m-tree 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.