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 semver from 7.3.7 to 7.6.1 #77

Closed
wants to merge 1 commit into from

Conversation

NOUIY
Copy link
Owner

@NOUIY NOUIY commented May 30, 2024

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 semver from 7.3.7 to 7.6.1.

ℹ️ 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 9 versions ahead of your current version.

  • The recommended version was released on 23 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
696 Proof of Concept
Release notes
Package name: semver from semver 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.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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 semver from 7.3.7 to 7.6.1.

See this package in npm:
semver

See this project in Snyk:
https://app.snyk.io/org/nexuscompute/project/f19ac175-c26b-43f9-a21f-9ded168131ce?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

guardrails bot commented May 30, 2024

⚠️ We detected 7 security issues in this pull request:

Vulnerable Libraries (7)
Severity Details
Medium pkg:npm/eslint@8.20.0 (t) upgrade to: > 8.20.0
High pkg:npm/@babel/core@7.18.9 (t) upgrade to: > 7.18.9
Medium pkg:npm/@babel/eslint-parser@7.18.9 (t) upgrade to: > 7.18.9
Medium pkg:npm/java-caller@2.4.0 (t) upgrade to: > 2.4.0
Critical pkg:npm/ip@1.1.8 (t) - no patch available
High pkg:npm/amplitude@5.2.0 (t) upgrade to: > 5.2.0
Medium pkg:npm/axios@0.21.4 (t) upgrade to: 1.6.0

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

Copy link

github-actions bot commented May 30, 2024

🦙 MegaLinter status: ❌ ERROR

Descriptor Linter Files Fixed Errors Elapsed time
✅ DOCKERFILE hadolint 1 0 0.06s
✅ GROOVY npm-groovy-lint 1 0 0 12.97s
✅ JAVASCRIPT eslint 98 0 0 4.59s
✅ JSON eslint-plugin-jsonc 9 0 0 2.09s
✅ JSON jsonlint 9 0 0.21s
✅ JSON npm-package-json-lint yes no 0.64s
✅ JSON prettier 9 0 0 1.78s
❌ JSON v8r 9 1 12.78s
⚠️ MARKDOWN markdownlint 6 2 10 1.24s
✅ MARKDOWN markdown-link-check 6 0 1.03s
✅ MARKDOWN markdown-table-formatter 6 2 0 0.59s
❌ REPOSITORY checkov yes 6 10.64s
✅ REPOSITORY gitleaks yes no 8.9s
✅ REPOSITORY git_diff yes no 0.12s
✅ REPOSITORY secretlint yes no 1.64s
❌ SPELL cspell 119 1 6.65s
✅ SPELL misspell 118 0 0 0.24s
✅ YAML prettier 3 0 0 0.7s
✅ YAML v8r 3 0 9.39s
✅ YAML yamllint 3 0 0.28s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

Copy link

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this pull request should stay open, please remove the O: stale 🤖 label or comment on the pull request.

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

Successfully merging this pull request may close these issues.

2 participants