npm install @peterpme/parse-server-mailgun
The npm package @peterpme/parse-server-mailgun receives a total of 0 downloads a week. As such, we scored @peterpme/parse-server-mailgun popularity level to be Limited.
Based on project statistics from the GitHub repository for the npm package @peterpme/parse-server-mailgun, we found that it has been starred 55 times, and that 2 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 @peterpme/parse-server-mailgun 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 @peterpme/parse-server-mailgun is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test @peterpme/parse-server-mailgun
Further analysis of the maintenance status of @peterpme/parse-server-mailgun 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 @peterpme/parse-server-mailgun 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 @peterpme/parse-server-mailgun is missing a Code of Conduct.
We detected a total of 375 direct & transitive dependencies for @peterpme/parse-server-mailgun. See the full dependency tree of @peterpme/parse-server-mailgun
@peterpme/parse-server-mailgun 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.