@qwick/future

v2.3.2-qwick.2

A Js.Promise alternative for ReasonML.

MIT
Latest version published 2 years ago
    npm install @qwick/future
  

Package Health Score

52 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Limited
Download trend

Weekly Downloads (1)

Dependents
15
GitHub Stars
217
Forks
15
Contributors
20

The npm package @qwick/future receives a total of 1 downloads a week. As such, we scored @qwick/future popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @qwick/future, we found that it has been starred 217 times, and that 15 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

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

01/2019

Direct Vulnerabilities

Popular
2.3.2-qwick.2
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
2.3.2-qwick.2
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
2.3.2-qwick.2
  • 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 @qwick/future 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 @qwick/future
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
8
Open PR
1
Last Release
2 years ago
Last Commit
12 months ago

Further analysis of the maintenance status of @qwick/future 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 @qwick/future 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

Sustainable
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

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

How about a good first contribution to this project? It seems that @qwick/future is missing a README file.


Embed Package Health Score Badge

package health: 52/100 package health 52/100

Package

Node.js Compatibility
not defined

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

@qwick/future 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.