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 @slack/client from 3.16.0 to 5.0.2 #3

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

Conversation

fsrocha-dev
Copy link

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


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
critical severity 858/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 9.3
Authentication Bypass
SNYK-JS-HAWK-6969142
Yes Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: @slack/client The new version differs by 250 commits.

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Authentication Bypass

@backstage-rdstation
Copy link

Olá!

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

Para melhorar, é importante incluir o motivo da mudança, o contexto histórico ou a justificativa da alteração, além de fornecer instruções claras sobre como testar o pull request na prática. Isso ajudará a equipe a entender melhor o impacto da alteração e a testá-la de forma eficaz.

Se precisar de ajuda para aprimorar a descrição, estou à disposição. Obrigado pela colaboraçã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
3 participants