Skip to content
New issue

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

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

Already on GitHub? # to your account

[Snyk] Security upgrade bootstrap from 4.6.0 to 5.0.0 #432

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

Snyk changed the following file(s):

  • frontend/package.json
  • frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Cross-site Scripting (XSS)
SNYK-JS-BOOTSTRAP-7444580
  688  
medium severity Cross-site Scripting
SNYK-JS-BOOTSTRAP-7444617
  688  

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:

🦉 Cross-site Scripting (XSS)

@backstage-rdstation
Copy link

Olá!

Obrigado por enviar o pull request para corrigir as vulnerabilidades nas dependências do projeto. No entanto, para melhorar a qualidade da descrição do pull request, sugiro adicionar mais informações.

Você poderia explicar de forma clara o motivo da correção das vulnerabilidades, incluindo o contexto histórico da mudança, a justificativa da correção e o racional por trás dela. Além disso, seria útil incluir um passo a passo ou instruções de teste para facilitar a revisão e validação do pull request.

Essas melhorias ajudarão a tornar a descrição do pull request mais completa e informativa. Obrigado pelo seu trabalho e continue contribuindo de forma colaborativa!

Esse comentário foi gerado por inteligência artificial

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

Successfully merging this pull request may close these issues.

3 participants