hyperkv

v2.1.1

p2p key/value store over a [hyperlog][1] using a [multi-value register conflict strategy][2]

BSD-2-Clause
Latest version published 3 years ago
    npm install hyperkv
  
We couldn't find any similar packages Browse all packages

Package Health Score

49 / 100

Security

No known security issues
Powered by Snyk
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.1.1 | 04/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.5 | 04/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.6.1 | 02/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.7.1 | 11/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.5.3 | 08/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-2-Clause
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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test hyperkv
Get started free

Popularity

Limited

Weekly Downloads (42)

Download trend
Dependents
12
GitHub Stars
126
Forks
12
Contributors
6

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package hyperkv, we found that it has been starred 126 times, and that 12 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
6
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 49/100 package health 49/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of hyperkv 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 hyperkv 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
7 years
Dependencies
17 Direct
Versions
21
Install Size
40.8 kB
Dist-tags
1
# of Files
21
Maintainers
2
TS Typings
No

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