hyperswarm

v4.3.5

A distributed networking stack for connecting peers For more information about how to use this package see README

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

74 / 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
4.3.5 | 09/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.2.0 | 07/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.4 | 04/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.15.3 | 01/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.14.2 | 07/2020
  • 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 (853)

Download trend
Dependents
66
GitHub Stars
899
Forks
64
Contributors
20

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package hyperswarm, we found that it has been starred 899 times, and that 66 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
20
Funding
No

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


Embed Package Health Score Badge

package health: 74/100 package health 74/100

Maintenance

Healthy

Commit Frequency

Open Issues
24
Open PR
2
Last Release
2 months ago
Last Commit
2 months ago

Further analysis of the maintenance status of hyperswarm based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that hyperswarm demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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
8 years
Dependencies
5 Direct
Versions
62
Install Size
33.7 kB
Dist-tags
2
# of Files
9
Maintainers
4
TS Typings
No

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