key-did-resolver

v4.0.0

Ceramic did:key method resolver For more information about how to use this package see README

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

72 / 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
4.0.0 | 01/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.0 | 02/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.3.0 | 10/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.4 | 01/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.1 | 08/2021
  • 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

Small

Weekly Downloads (5,122)

Download trend
GitHub Stars
96
Forks
28
Contributors
20

Direct Usage Popularity

TOP 30%

The npm package key-did-resolver receives a total of 5,122 downloads a week. As such, we scored key-did-resolver popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package key-did-resolver, we found that it has been starred 96 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
No

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


Embed Package Health Score Badge

package health: 72/100 package health 72/100

Maintenance

Sustainable

Commit Frequency

Open Issues
6
Open PR
12
Last Release
11 months ago
Last Commit
1 month ago

Further analysis of the maintenance status of key-did-resolver based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that key-did-resolver demonstrates a positive version release cadence with at least one new version released in the past 12 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
>=14.14

Age
4 years
Dependencies
4 Direct
Versions
63
Install Size
33.7 kB
Dist-tags
2
# of Files
14
Maintainers
6
TS Typings
No

key-did-resolver 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.