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] Security upgrade webpack from 4.44.2 to 5.1.1 #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andersonsevla
Copy link

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 fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818
  479  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

@backstage-rdstation
Copy link

Olá!

Obrigado por enviar o pull request para corrigir as vulnerabilidades nas dependências do projeto. No entanto, sua descrição não atende aos critérios estabelecidos para uma boa descrição de pull request.

Para melhorar, sugiro que você inclua uma explicação clara do motivo da mudança e também um passo a passo para testar o pull request na prática. Isso ajudará a equipe a entender melhor o contexto da alteração e a testar as mudanças de forma eficiente.

Lembre-se da importância de fornecer informações detalhadas e claras em suas descrições de pull request. Estamos aqui para ajudar e colaborar juntos!

Se precisar de mais orientações, estou à disposição.

Esse comentário foi gerado por inteligência artificial

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.

3 participants