cosign

v0.2.1

Bitcoin Transaction Tool

MIT
Latest version published 8 years ago
    npm install cosign
  

Package Health Score

57 / 100

Popularity

Small

Weekly Downloads (7)

Download trend
Dependents
0
GitHub Stars
3.3K
Forks
1.71K
Contributors
90

Direct Usage Popularity


The npm package cosign receives a total of 7 downloads a week. As such, we scored cosign popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package cosign, we found that it has been starred 3,297 times, and that 0 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

12/2013
02/2014

Direct Vulnerabilities

0.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.2.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular

License Risk

0.0.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.2.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

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


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

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

Maintenance

Inactive

Commit Frequency

Open Issues
312
Open PR
7
Last Release
8 years ago
Last Commit
3 days ago

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

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
90
Funding
No

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


Embed Package Health Score Badge

package health: 57/100 package health 57/100

Package

Node.js Compatibility
>=0.8

Age
8 years
Dependencies
8 Direct
Versions
3
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
2
TS Typings
No

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