sha256

v0.2.0

Compute SHA256 of bytes or strings.

Latest version published over 5 years ago
    npm install sha256
  

Package Health Score

54 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Recognized
Weekly Downloads (27,910)
Dependents
377
GitHub Stars
41
Forks
22
Contributors
5

The npm package sha256 receives a total of 27,910 downloads a week. As such, we scored sha256 popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package sha256, we found that it has been starred 41 times, and that 377 other projects on 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.

Security

No known security issues

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.1.1
0.2.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.1.1
0.2.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.1.1
0.2.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like sha256 is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test sha256
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
4
Merged PR
4
Open PR
0
Last Commit
4 years ago

Further analysis of the maintenance status of sha256 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 sha256 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.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
5
Funding
No
License
Unknown

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that sha256 is missing a LICENSE file.


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
2 Direct / 2 Total
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
4
TS Typings
Yes

We detected a total of 2 direct & transitive dependencies for sha256. See the full dependency tree of sha256

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