q-io

v1.13.6

IO using Q promises

MIT
Latest version published over 2 years ago
    npm install q-io
  
We couldn't find any similar packages Browse all packages

Package Health Score

53 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    Security review needed
  • Community
    Sustainable

Popularity

Recognized
Weekly Downloads (37,472)
Dependents
348
GitHub Stars
315
Forks
72
Contributors
20

The npm package q-io receives a total of 37,472 downloads a week. As such, we scored q-io popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package q-io, we found that it has been starred 315 times, and that 348 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

Security review needed

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.18
1.12.0
1.13.6
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.18
1.12.0
1.13.6
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.18
1.12.0
1.13.6
  • 0
    H
  • 0
    M
  • 0
    L
  • 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

Snyk detected that the latest version of q-io has a security vulnerability.

We highly advise you to review these security issues.

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 q-io is missing a security policy.

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

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
23
Merged PR
71
Open PR
5
Last Commit
2 years ago

Further analysis of the maintenance status of q-io 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 q-io 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
License
MIT

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Package

Node.js Compatibility
>=0.6.0

Age
10 years
Dependencies
6 Direct / 16 Total
Versions
3
Install Size
190 kB
Dist-tags
2
# of Files
34
Maintainers
5
TS Typings
Yes

We detected a total of 16 direct & transitive dependencies for q-io. See the full dependency tree of q-io

q-io 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.