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] Upgrade sequelize-typescript from 2.1.3 to 2.1.6 #4

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

Conversation

lunoon
Copy link
Owner

@lunoon lunoon commented Nov 12, 2024

snyk-top-banner

Snyk has created this PR to upgrade sequelize-typescript from 2.1.3 to 2.1.6.

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

  • The recommended version was released on a year ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Prototype Pollution
SNYK-JS-SEQUELIZETYPESCRIPT-6085300
696 Proof of Concept
Release notes
Package name: sequelize-typescript from sequelize-typescript 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 sequelize-typescript from 2.1.3 to 2.1.6.

See this package in npm:
sequelize-typescript

See this project in Snyk:
https://app.snyk.io/org/lunoon/project/df4b8ca1-e11e-4625-8db5-57edad7b0688?utm_source=github&utm_medium=referral&page=upgrade-pr
# 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.

2 participants