run-dbcan

v3.0.0

Standalone version of dbCAN annotation tool for automated CAZyme annotation For more information about how to use this package see README

Latest version published 3 years ago
License: GPL-3.0

Ensure you're using the healthiest python packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

43 / 100

Explore Similar Packages

Popularity

Limited
GitHub Stars
145
Forks
40
Contributors
10

Direct Usage Popularity


Based on project statistics from the GitHub repository for the PyPI package run-dbcan, we found that it has been starred 145 times.

Security

Security review needed
Powered by Snyk
3.0.0 (Latest)

Security and license risk for latest version

Release Date
Dec 20, 2021
Direct Vulnerabilities
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Indirect Vulnerabilities
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
License Risk
  • 1
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
GPL-3.0
Alert

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.


Security Policy
No

We found a way for you to contribute to the project! Looks like run-dbcan 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.

Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
41
Open PR
1
Last Release
3 years ago
Last Commit
7 months ago

Further analysis of the maintenance status of run-dbcan based on released PyPI versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for run-dbcan is that it hasn't seen any new versions released to PyPI 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

Sustainable
Readme
Yes
Contributing.md
No
Code of Conduct
No
Contributors
10
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 43/100 package health 43/100

Package

Python Versions Compatibility
>=3

Age
5 years
Latest Release
3 years ago
Dependencies
5 Direct / 5 Total
Versions
14
Maintainers
1
Wheels
OS Independent