ipfs-interop

v10.2.0

Interoperability Tests for IPFS For more information about how to use this package see README

Latest version published 2 years ago
License: Apache-2.0 OR 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

39 / 100

Explore Similar Packages

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
10.1.0 | 05/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.2.0 | 05/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.0.1 | 02/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.2.0 | 11/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.0.11 | 09/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0 OR 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 (346)

Download trend
GitHub Stars
32
Forks
15
Contributors
30

Direct Usage Popularity

Occasionally

The npm package ipfs-interop receives a total of 346 downloads a week. As such, we scored ipfs-interop popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package ipfs-interop, we found that it has been starred 32 times.

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

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


Embed Package Health Score Badge

package health: 39/100 package health 39/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
12
Open PR
17
Last Release
2 years ago
Last Commit
1 year ago

Further analysis of the maintenance status of ipfs-interop 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 ipfs-interop 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
>=16.0.0

Age
5 years
Dependencies
41 Direct
Versions
55
Install Size
2.16 MB
Dist-tags
1
# of Files
90
Maintainers
5
TS Typings
No

ipfs-interop 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.