npm install strapi-email-nodemailer-fork
The npm package strapi-email-nodemailer-fork receives a total of 24 downloads a week. As such, we scored strapi-email-nodemailer-fork popularity level to be Limited.
Based on project statistics from the GitHub repository for the npm package strapi-email-nodemailer-fork, we found that it has been starred ? times, and that 0 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.
Snyk detected that the latest version of strapi-email-nodemailer-fork 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 strapi-email-nodemailer-fork is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test strapi-email-nodemailer-fork
Further analysis of the maintenance status of strapi-email-nodemailer-fork 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 strapi-email-nodemailer-fork 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.
This project has seen only 10 or less contributors.
We found a way for you to contribute to the project! Looks like strapi-email-nodemailer-fork is missing a Code of Conduct.
We detected a total of 1 direct & transitive dependencies for strapi-email-nodemailer-fork. See the full dependency tree of strapi-email-nodemailer-fork
strapi-email-nodemailer-fork 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.