Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade cronstrue from 2.27.0 to 2.50.0 #3708

Closed

Conversation

prernaadev01
Copy link
Collaborator

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade cronstrue from 2.27.0 to 2.50.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 23 versions ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: cronstrue from cronstrue GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade cronstrue from 2.27.0 to 2.50.0.

See this package in npm:
cronstrue

See this project in Snyk:
https://app.snyk.io/org/prernaadev01/project/a463ee50-a418-4f8b-a9cb-b5cb99cec8fe?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

Unit Test Results

27 tests  ±0   27 ✔️ ±0   0s ⏱️ ±0s
27 suites ±0     0 💤 ±0 
  3 files   ±0     0 ±0 

Results for commit a4aa3e1. ± Comparison against base commit bbdd402.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants