multilevel

v7.2.3

Expose a leveldb over the network. 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

42 / 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
7.2.3 | 02/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.2.1 | 09/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
7.1.0 | 09/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.6.0 | 04/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.5.0 | 08/2013
  • 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 (84)

Download trend
GitHub Stars
354
Forks
34
Contributors
20

Direct Usage Popularity

Occasionally

The npm package multilevel receives a total of 84 downloads a week. As such, we scored multilevel popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package multilevel, we found that it has been starred 354 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
20
Funding
Yes

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


Embed Package Health Score Badge

package health: 42/100 package health 42/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
13
Open PR
3
Last Release
6 years ago
Last Commit
6 years ago

Further analysis of the maintenance status of multilevel 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 multilevel 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
>0.6

Age
11 years
Dependencies
6 Direct
Versions
46
Install Size
42.7 kB
Dist-tags
2
# of Files
38
Maintainers
1
TS Typings
No

multilevel 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.